Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 361868 - Deadlock when workbench is terminated
Summary: Deadlock when workbench is terminated
Status: CLOSED FIXED
Alias: None
Product: Tigerstripe
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 major (vote)
Target Milestone: 0.5M0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-24 16:32 EDT by Navid Mehregani CLA
Modified: 2011-11-03 11:29 EDT (History)
0 users

See Also:

Attachments
Thread dump (24.10 KB, text/plain)
2011-10-24 16:33 EDT, Navid Mehregani 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 Navid Mehregani CLA 2011-10-24 16:32:27 EDT 
Build Identifier: 

In some cases when Tigerstripe workbench is terminated (by killing the process), it's no longer possible to launch the workbench with the same workspace.  It seems to deadlock on workbench startup.  Please see attached thread dump for more details.  In particular look at the following threads:

Daemon Thread [Thread-1] and Thread [Worker-0] 



Reproducible: Always

Steps to Reproduce:
1. Launch a runtime instance of Tigerstripe.  Checkout a few projects
2. Terminate the workbench by killing the process
3. Relaunch Tigerstripe in the same workspace
Comment 1 Navid Mehregani CLA 2011-10-24 16:33:16 EDT 
Created attachment 205867 [details]
Thread dump
Comment 2 Navid Mehregani CLA 2011-11-03 11:29:05 EDT 
Fixed and verified. Thanks!