Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 341901

Summary: [implementation] Deadlock in SharedASTProvider.getAST() (on BreakpointMarkerUpdater.updateMarker)
Product: [Eclipse Project] JDT Reporter: Jörg Thönnes <jtk499>
Component: TextAssignee: JDT-Text-Inbox <jdt-text-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: critical    
Priority: P3 CC: b.muskalla, daniel_megert
Version: 3.6   
Target Milestone: ---   
Hardware: PC   
OS: Linux-GTK   
Whiteboard:
Attachments:
Description Flags
Stack trace on console
none
jstack output none

Description Jörg Thönnes CLA 2011-04-05 09:21:41 EDT 
Cloned from: 318797: [implementation] Deadlock in SharedASTProvider.getAST()  (on breakpoint creation)
https://bugs.eclipse.org/bugs/show_bug.cgi?id=318797

This looks like the above bug, but the stack trace is different. See attached files.
Comment 1 Dani Megert CLA 2011-04-05 09:22:59 EDT 
Which build id?
Please attach the full stack trace.
Comment 2 Jörg Thönnes CLA 2011-04-05 09:26:20 EDT 
This is the released Eclipse 3.6.0 JEE package. Where can I find the build id?
Comment 3 Jörg Thönnes CLA 2011-04-05 09:27:17 EDT 
Created attachment 192553 [details]
Stack trace on console
Comment 4 Jörg Thönnes CLA 2011-04-05 09:27:46 EDT 
Created attachment 192554 [details]
jstack output
Comment 5 Dani Megert CLA 2011-04-05 09:29:53 EDT 
The bug got fixed in 3.6.1 hence it's well possible you see it in 3.6.0.

*** This bug has been marked as a duplicate of bug 318797 ***
Comment 6 Jörg Thönnes CLA 2011-04-05 09:32:27 EDT 
(In reply to comment #5)
> The bug got fixed in 3.6.1 hence it's well possible you see it in 3.6.0.
> 
> *** This bug has been marked as a duplicate of bug 318797 ***

Thanks for the swift reply. I was not sure since the stack trace is a bit different.
Comment 7 Dani Megert CLA 2011-04-05 09:42:22 EDT 
We also fixed another deadlock in 3.7 M6 (see bug 322914).
Comment 8 Dani Megert CLA 2011-05-22 14:38:34 EDT 
*** Bug 346782 has been marked as a duplicate of this bug. ***