Bug 376545 - Freeze at org.eclipse.jdt.internal.ui.javaeditor.ASTProvider.getAST
Summary: Freeze at org.eclipse.jdt.internal.ui.javaeditor.ASTProvider.getAST
Status: CLOSED DUPLICATE of bug 366048
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.8   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-11 18:46 EDT by Stephan Herrmann CLA
Modified: 2012-04-12 09:03 EDT (History)
1 user (show)

See Also:


Attachments
stack dump (37.75 KB, text/plain)
2012-04-11 18:46 EDT, Stephan Herrmann CLA
no flags Details
first stack dump (43.02 KB, text/plain)
2012-04-11 18:49 EDT, Stephan Herrmann CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stephan Herrmann CLA 2012-04-11 18:46:38 EDT
Created attachment 213869 [details]
stack dump

SDK 3.8 Build id: I20120125-1800

In the background JUnit Plug-in Tests were running.
I was trying to continue browsing code and expanding items in the JUnit view.
I think it was at the expand click that the busy cursor appeared, and Eclipse froze. I killed the debug target, but still Eclipse would not unfreeze.

Attaching stack traces after killing the debug target. A few debug related threads had disappeared by then but the following threads have not changed since the freeze:
"Worker-79"
"Worker-73"
"main"
all of which are interested in the same lock object.

Although I see a key event in the stack I can't recall using the keyboard at that time but recollection is blurred by the fact that I was also switching virtual desktops and just came back to Eclipse at what time it wouldn't respond to the next click.
Comment 1 Stephan Herrmann CLA 2012-04-11 18:49:25 EDT
Created attachment 213870 [details]
first stack dump

OK, I also have a dump from when the debugger was still running. Most threads show no difference between both dumps.
Comment 2 Dani Megert CLA 2012-04-12 09:03:23 EDT

*** This bug has been marked as a duplicate of bug 366048 ***