Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 335656 - Deadlock in ASTProvider
Summary: Deadlock in ASTProvider
Status: CLOSED DUPLICATE of bug 322914
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.6.1   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-28 02:47 EST by Mikko Tiihonen CLA
Modified: 2011-01-28 10:13 EST (History)
1 user (show)

See Also:


Attachments
Stack trace of deadlock (34.27 KB, text/plain)
2011-01-28 02:48 EST, Mikko Tiihonen CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mikko Tiihonen CLA 2011-01-28 02:47:09 EST
Build Identifier: 

Deadlock right after workspace had been opened and I tried to select a piece of code by double-clicking it.

In the stacktrace you can see that there following plugins are initializing:
moreunit, m2eclipse, subversive

There is no direct deadlock but could it be that the main thread swt code plus the swt code that the subversive plugin are somehow indirectly blocking each other.

Reproducible: Didn't try
Comment 1 Mikko Tiihonen CLA 2011-01-28 02:48:07 EST
Created attachment 187808 [details]
Stack trace of deadlock
Comment 2 Dani Megert CLA 2011-01-28 03:21:27 EST

*** This bug has been marked as a duplicate of bug 318797 ***
Comment 3 Mikko Tiihonen CLA 2011-01-28 10:06:27 EST
My build is M20101222-0800 aka 3.6.2 snapshot.

This is much newer release than bug 318797 which has been marked:
- Fixed in R3_6_maintenance.
- Available in builds >= M20100825-0800.

So I think my stacktrace is either an another bug or the bug 318797 needs to be reopened.
Comment 4 Dani Megert CLA 2011-01-28 10:13:35 EST
(In reply to comment #3)
> My build is M20101222-0800 aka 3.6.2 snapshot.
Why not tell the first time? Why set the version to 4.1?

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