Bug 401045 - Indefinite wait() in SharedASTProvider.getAST()
Summary: Indefinite wait() in SharedASTProvider.getAST()
Status: CLOSED DUPLICATE of bug 366048
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.8.1   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-18 03:25 EST by Jörg von Frantzius CLA
Modified: 2013-02-18 04:42 EST (History)
1 user (show)

See Also:


Attachments
Full thread dump (44.11 KB, text/plain)
2013-02-18 03:25 EST, Jörg von Frantzius CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jörg von Frantzius CLA 2013-02-18 03:25:19 EST
Created attachment 227180 [details]
Full thread dump

My installation of Eclipse 4.2.1 with "      Eclipse Java Development Tools	3.8.1.v20120814-104540-8-8nFqpFNOfwKDRVz-tXOcL5d_83	org.eclipse.jdt.feature.group	Eclipse.org" just locked up when I pressed Ctrl+O for opening an outline within the Java editor.

The thread dump I took shows several threads like this:

"Text Viewer Hover Presenter" daemon prio=10 tid=0x00007f0d19fc8800 nid=0x5b8e in Object.wait() [0x00007f0e3f5fb000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        - waiting on <0x00000000a28a3d40> (a java.lang.Object)
        at java.lang.Object.wait(Object.java:503)
        at org.eclipse.jdt.internal.ui.javaeditor.ASTProvider.getAST(ASTProvider.java:457)
        - locked <0x00000000a28a3d40> (a java.lang.Object)
        at org.eclipse.jdt.ui.SharedASTProvider.getAST(SharedASTProvider.java:128)

with different entries into that method. It seems that Object.wait() is called, but nothing happens to wake up the thread.

I haven't had this repeatedly yet, only one occasion so far. Still seems to prove that something is likely wrong in synchronization code (and may ask for standard multithreading library calls :)
Comment 1 Dani Megert CLA 2013-02-18 04:07:35 EST
Full stack trace and steps would be great.

*** This bug has been marked as a duplicate of bug 366048 ***
Comment 2 Jörg von Frantzius CLA 2013-02-18 04:42:06 EST
Sorry, I don't have steps to reproduce, should I say luckily, as it happened only once so far to me :)

For full stack trace please see attachment to this issue: https://bugs.eclipse.org/bugs/attachment.cgi?id=227180