Bug 406404 - Deadlock while accessing TransactionUtil.runExclusive
Summary: Deadlock while accessing TransactionUtil.runExclusive
Status: CLOSED WONTFIX
Alias: None
Product: Sphinx
Classification: Automotive
Component: Core (show other bugs)
Version: 0.7.0   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 406403 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-04-24 05:11 EDT by Vimal Nair CLA
Modified: 2024-05-07 00:11 EDT (History)
4 users (show)

See Also:

Attachments
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 Vimal Nair CLA 2013-04-24 05:11:42 EDT 
We could find a deadlock in Sphinx. Please find the attached thread dump. 
 
Main Thread does first lock the autosar model:
         at org.eclipse.emf.transaction.util.TransactionUtil.runExclusive(TransactionUtil.java:328)
 
and later tries to get a lock to one particular resource:
 
        at org.eclipse.core.internal.resources.Resource.refreshLocal(Resource.java:1692)
 
(and waits forever).
 
 
Worker 18 is a job with scheduling rule including the project:
 
        at org.eclipse.sphinx.emf.workspace.loading.ModelLoadManager$2.run(ModelLoadManager.java:533)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
 
and later tries:
 
        at org.eclipse.emf.transaction.impl.TransactionalEditingDomainImpl.runExclusive(TransactionalEditingDomainImpl.java:321)
Comment 1 Vimal Nair CLA 2013-04-24 05:13:07 EDT 
Stephen suspects this issue relates to https://bugs.eclipse.org/bugs/show_bug.cgi?id=374883
Comment 2 Stephan Eberle CLA 2013-08-02 06:33:23 EDT 
*** Bug 406403 has been marked as a duplicate of this bug. ***
Comment 3 Balazs Grill CLA 2024-05-07 00:11:14 EDT 
Closed stale issue before migration