Summary: | Deadlock when trying to find the implementation of a method. | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Udo Walker <udo.walker> |
Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
Status: | NEW --- | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | loskutov, slawas, stephan.herrmann |
Version: | 4.7 | Keywords: | needinfo |
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows 10 | ||
Whiteboard: | stalebug |
Description
Udo Walker
2017-07-21 02:00:07 EDT
My Eclipse version: eclipse.buildId=4.7.0.I20170612-0950 java.version=1.8.0_91 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_DE Udo, please next time attach the log, not paste it as a comment, it is really hard to read :-) Do you have steps to reproduce? If not, but you still observe the problem, please next time it hangs, create *few* jstack dump files and attach them here. Ok, I did not know jstack but will use it next time. Thanks. similar to bug 366048 but seemingly without the pattern of a stack growing an additional frame every 30 seconds? Hi, I have a same problem. Is any woraround? My threads: --------------------- "Worker-22" #471 prio=5 os_prio=0 tid=0x0000000029b11000 nid=0x3e2c waiting for monitor entry [0x000000005722f000] java.lang.Thread.State: BLOCKED (on object monitor) at org.eclipse.jdt.internal.ui.viewsupport.SelectionListenerWithASTManager$PartListenerGroup$3.run(SelectionListenerWithASTManager.java:158) - waiting to lock <0x00000006cc506960> (a java.lang.Object) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) Locked ownable synchronizers: - None --------------------- locked by: "Worker-18" #81 prio=5 os_prio=0 tid=0x0000000029b0f000 nid=0x724 in Object.wait() [0x00000000411af000] java.lang.Thread.State: TIMED_WAITING (on object monitor) at java.lang.Object.wait(Native Method) at org.eclipse.jdt.internal.ui.javaeditor.ASTProvider.getAST(ASTProvider.java:458) - locked <0x00000006c486b010> (a java.lang.Object) at org.eclipse.jdt.internal.ui.javaeditor.ASTProvider.getAST(ASTProvider.java:471) at org.eclipse.jdt.ui.SharedASTProvider.getAST(SharedASTProvider.java:128) at org.eclipse.jdt.internal.ui.viewsupport.SelectionListenerWithASTManager$PartListenerGroup.calculateASTandInform(SelectionListenerWithASTManager.java:173) at org.eclipse.jdt.internal.ui.viewsupport.SelectionListenerWithASTManager$PartListenerGroup$3.run(SelectionListenerWithASTManager.java:158) - locked <0x00000006cc506960> (a java.lang.Object) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) Locked ownable synchronizers: - None (In reply to Sławomir Cichy from comment #5) > Hi, > > I have a same problem. Is any woraround? > My threads: > --------------------- > "Worker-22" #471 prio=5 os_prio=0 tid=0x0000000029b11000 nid=0x3e2c waiting > for monitor entry [0x000000005722f000] > java.lang.Thread.State: BLOCKED (on object monitor) > at /trunc/ I forgot. My Eclipse: Version: Oxygen.3a Release (4.7.3a) Build id: 20180405-1200 (In reply to Sławomir Cichy from comment #5) The following applies to all users seeing this issue: (In reply to Andrey Loskutov from comment #2) > Do you have steps to reproduce? > If not, but you still observe the problem, please next time it hangs, create > *few* jstack dump files and attach them here. 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. If you have further information on the current state of the bug, please add it. 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. 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. If you have further information on the current state of the bug, please add it. 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. |