Bug 238370 - deadlock in JavaReconciler
Summary: deadlock in JavaReconciler
Status: RESOLVED DUPLICATE of bug 239230
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-24 23:14 EDT by Michael Scharf CLA
Modified: 2008-09-02 05:36 EDT (History)
5 users (show)

See Also:

Attachments
the stack trace where it is hanging (33.92 KB, text/plain)
2008-06-24 23:14 EDT, Michael Scharf CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Scharf CLA 2008-06-24 23:14:17 EDT 
Created attachment 105780 [details]
the stack trace where it is hanging

It happens with different versions of eclipse (including ganymede).

When I start eclipse and I have some editors open I get this deadlock.

The problem is that JavaReconciler starts the clearcase plugin and this plugin does a Display.syncExec. This is questionable but maybe JDT can do something to prevent this happening....

To start eclipse when this happens:
- disable or remove the ccase plugins from you eclipse
  (or use a eclipse without ccase)
- start eclipse
- close all editors
- enable ccase
- start eclipse
Comment 1 Dani Megert CLA 2008-06-25 10:52:55 EDT 
>The problem is that JavaReconciler starts the clearcase plugin and this plugin
>does a Display.syncExec. This is questionable but maybe JDT can do something to
>prevent this happening....
Definitely questionable. Did you file a bug report against the Clearcase provider?


It looks like the same init code (JavaModelManager.initializeAllContainers) is executed from two different threads (UI and reconciler). This seems strange.
Comment 2 Michael Scharf CLA 2008-06-25 13:12:04 EDT 
I posted a bug report at the ccase forum
  http://www-128.ibm.com/developerworks/forums/thread.jspa?threadID=211616
Comment 3 Dani Megert CLA 2008-06-30 04:45:18 EDT 
See also bug 236954.
Comment 4 Jerome Lanneluc CLA 2008-08-12 06:00:56 EDT 
The deadlock seems to be caused by the call to org.eclipse.core.internal.resources.Rules.modifyRule(Rules.java:136) in the "main" thread. This call acquires a lock. I would not expect such a call to acquire a lock. John, Szymon, is this per design?
Comment 5 Jerome Lanneluc CLA 2008-08-12 11:24:19 EDT 
Actually, it might be more a dup of bug 239230 ([Workbench] Deadlock due to lock owner peforming syncExec during startup).

Depending on the answer to comment 4, I'll mark it as a dup.
Comment 6 Jerome Lanneluc CLA 2008-09-02 05:36:17 EDT 
Moving to Platform/UI
Comment 7 Jerome Lanneluc CLA 2008-09-02 05:36:43 EDT 

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