| Summary: | Intermittent hanging when editing java files in eclipse | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | tony tony <xxteknolustxx> | ||||||
| Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | jarthana, timo.kinnunen | ||||||
| Version: | 3.7.2 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows 7 | ||||||||
| Whiteboard: | stalebug | ||||||||
| Attachments: |
|
||||||||
|
Description
tony tony
Created attachment 233856 [details]
recent_eclipse_hang_7_27_2013_thread_dump
Again eclipse was hanging, however lately I've been unable to get multiple thread dumps during the intermittent hang.
When I try to use jstack to attach to the java process from eclipse, jstack will just hang (used jstack -F <pid> >> dump.txt).
See recent attachment, it is the thread dump right as eclipse becomes usable again.
Below is what jstack (jdk 1.7.0_21) threw up at me:
Attaching to process ID 3416, please wait...
Debugger attached successfully.
Server compiler detected.
JVM version is 23.21-b01
sun.jvm.hotspot.debugger.DebuggerException: Windbg Error: ReadVirtual failed!
at sun.jvm.hotspot.debugger.windbg.WindbgDebuggerLocal.readBytesFromProc
ess0(Native Method)
at sun.jvm.hotspot.debugger.windbg.WindbgDebuggerLocal.readBytesFromProc
ess(WindbgDebuggerLocal.java:485)
at sun.jvm.hotspot.debugger.DebuggerBase$Fetcher.fetchPage(DebuggerBase.
java:76)
at sun.jvm.hotspot.debugger.PageCache.getPage(PageCache.java:178)
at sun.jvm.hotspot.debugger.PageCache.getLong(PageCache.java:100)
at sun.jvm.hotspot.debugger.DebuggerBase.readCInteger(DebuggerBase.java:
356)
at sun.jvm.hotspot.debugger.DebuggerBase.readAddressValue(DebuggerBase.j
ava:454)
at sun.jvm.hotspot.debugger.windbg.WindbgDebuggerLocal.readAddress(Windb
gDebuggerLocal.java:316)
at sun.jvm.hotspot.debugger.windbg.WindbgAddress.getAddressAt(WindbgAddr
ess.java:72)
at sun.jvm.hotspot.debugger.cdbg.basic.amd64.AMD64CFrame.sender(AMD64CFr
ame.java:55)
at sun.jvm.hotspot.tools.PStack.run(PStack.java:161)
at sun.jvm.hotspot.tools.PStack.run(PStack.java:53)
at sun.jvm.hotspot.tools.PStack.run(PStack.java:48)
at sun.jvm.hotspot.tools.JStack.run(JStack.java:60)
at sun.jvm.hotspot.tools.Tool.start(Tool.java:221)
at sun.jvm.hotspot.tools.JStack.main(JStack.java:86)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at sun.tools.jstack.JStack.runJStackTool(JStack.java:136)
at sun.tools.jstack.JStack.main(JStack.java:102)
sun.jvm.hotspot.debugger.UnalignedAddressException: f0809abb
at sun.jvm.hotspot.debugger.windbg.WindbgDebuggerLocal$1.checkAlignment(
WindbgDebuggerLocal.java:104)
at sun.jvm.hotspot.debugger.DebuggerBase.readCInteger(DebuggerBase.java:
349)
at sun.jvm.hotspot.debugger.DebuggerBase.readAddressValue(DebuggerBase.j
ava:454)
at sun.jvm.hotspot.debugger.windbg.WindbgDebuggerLocal.readAddress(Windb
gDebuggerLocal.java:316)
at sun.jvm.hotspot.debugger.windbg.WindbgAddress.getAddressAt(WindbgAddr
ess.java:72)
at sun.jvm.hotspot.debugger.cdbg.basic.amd64.AMD64CFrame.sender(AMD64CFr
ame.java:55)
at sun.jvm.hotspot.tools.PStack.run(PStack.java:161)
at sun.jvm.hotspot.tools.PStack.run(PStack.java:53)
at sun.jvm.hotspot.tools.PStack.run(PStack.java:48)
at sun.jvm.hotspot.tools.JStack.run(JStack.java:60)
at sun.jvm.hotspot.tools.Tool.start(Tool.java:221)
at sun.jvm.hotspot.tools.JStack.main(JStack.java:86)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at sun.tools.jstack.JStack.runJStackTool(JStack.java:136)
at sun.tools.jstack.JStack.main(JStack.java:102)
sun.jvm.hotspot.debugger.UnalignedAddressException: 6461140000000065
at sun.jvm.hotspot.debugger.windbg.WindbgDebuggerLocal$1.checkAlignment(
WindbgDebuggerLocal.java:104)
at sun.jvm.hotspot.debugger.DebuggerBase.readCInteger(DebuggerBase.java:
349)
at sun.jvm.hotspot.debugger.DebuggerBase.readAddressValue(DebuggerBase.j
ava:454)
at sun.jvm.hotspot.debugger.windbg.WindbgDebuggerLocal.readAddress(Windb
gDebuggerLocal.java:316)
at sun.jvm.hotspot.debugger.windbg.WindbgAddress.getAddressAt(WindbgAddr
ess.java:72)
at sun.jvm.hotspot.debugger.cdbg.basic.amd64.AMD64CFrame.sender(AMD64CFr
ame.java:55)
at sun.jvm.hotspot.tools.PStack.run(PStack.java:161)
at sun.jvm.hotspot.tools.PStack.run(PStack.java:53)
at sun.jvm.hotspot.tools.PStack.run(PStack.java:48)
at sun.jvm.hotspot.tools.JStack.run(JStack.java:60)
at sun.jvm.hotspot.tools.Tool.start(Tool.java:221)
at sun.jvm.hotspot.tools.JStack.main(JStack.java:86)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at sun.tools.jstack.JStack.runJStackTool(JStack.java:136)
at sun.tools.jstack.JStack.main(JStack.java:102)
(In reply to comment #2) > Again eclipse was hanging, however lately I've been unable to get multiple > thread dumps during the intermittent hang. This one is different from the suspects in other dumps you shared. From the previous ones, it would appear that there is some file operation (external to the workspace) that is causing some delay. Could that be some resource being accessed over a network, such as a JVM library? Linked folders from a secondary harddrive that has been powered down due to inactivity could also do that, although that should hang for about 5 seconds rather than minutes. So, I made the following changes to my eclipse.ini -vm C:/Program Files/Java/jdk1.7.0_21/bin/java.exe -vmargs -Dosgi.requiredJavaVersion=1.6 I was using javaw.exe before and the osgi required version was 1.5 and I changed it to 1.6 I haven't seen a hang yet since these changes. Regarding - "This one is different from the suspects in other dumps you shared. From the previous ones, it would appear that there is some file operation (external to the workspace) that is causing some delay. Could that be some resource being accessed over a network, such as a JVM library?" - Eclipse IS stored on a drive that is not the boot partition drive, however nothing within the project file is referenced outside of the eclipse workspace, and the workspace is on the same drive. - Now I do have other projects in my workspace that are on OTHER non boot partition drives (a external hd in one case), can this affect my work in projects on the same drive as eclipse? Thanks! (In reply to comment #5) > - Now I do have other projects in my workspace that are on OTHER non boot > partition drives (a external hd in one case), can this affect my work in > projects on the same drive as eclipse? > I have seen in my own experience that having resources stored in an external device does slow things down (in my case it was an SSD). But I don't think it should cause a hang. Please continue to observe and update us when you see the problem again. I will keep this bug open for some more time. Created attachment 234002 [details]
Threaddump of Eclipse "Not Responding" while a harddrive is powering up
The brief hang is caused by the main thread opening a file while handling a keypress event. I have JDK source code folder on another drive and this happens when pressing F3 to open e.g. CharSequence.class from String.class. Changing power management options to shut down harddrives after 3 minutes instead of 20 minutes of inactivity makes reproducing this easier.
The same situation can also show up as content assist timing out and leaving an error message: The 'org.eclipse.recommenders.subwords.rcp.category' proposal computer from the 'org.eclipse.recommenders.completion.rcp.subwords' plug-in did not complete normally. The extension took too long to return from the 'computeCompletionProposals()' operation. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |