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

Bug 354490

Summary: Workspace failed to start due to Problems View getting activated outside SWT Display Thread
Product: [Eclipse Project] Platform Reporter: Remy Suen <remy.suen>
Component: UIAssignee: Platform-UI-Inbox <Platform-UI-Inbox>
Status: VERIFIED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: daniel_megert, mober.at+eclipse, pwebster, remy.suen
Version: 3.7   
Target Milestone: 3.8 M2   
Hardware: All   
OS: All   
Whiteboard:
Bug Depends on: 351212    
Bug Blocks:    

Description Remy Suen CLA 2011-08-11 09:18:53 EDT 
This clone is for tracking the fix in the 3.8 stream.

+++ This bug was initially created as a clone of Bug #351212 +++

Build ID: Eclipse 3.7 (Indigo)

1-time occurrence, see attached workspace log, here is my understanding of 
what happened:
- This was an existing fairly complex Indigo install with several dropins
- I added another *.link file to dropins (adding egit) and launched
- During launch, following exception was logged (p2 race condition?)
  org.osgi.framework.BundleException: State change in progress for bundle 
- Eclipse tried to bring up the Problems View
- But that failed due to org.eclipse.swt.SWTException: Invalid thread access
- Which caused the whole Eclipse Launch to terminate.

On relaunching, everything was fine so the config itself looked OK.

I'm reporting this since I've seen similar problems with the framework trying to activate the Problems View prematurely on other occasions too.
Comment 1 Eric Moffatt CLA 2011-08-17 14:09:09 EDT 
Committed in >20110817. Cherry picked the original patch to R3_development.
Comment 2 Dani Megert CLA 2011-08-19 05:55:42 EDT 
Verified in N20110818-2000.