Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 366110 - Eclipse appears to hang on startup if not in the foreground
Summary: Eclipse appears to hang on startup if not in the foreground
Status: CLOSED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.2   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 366114
  Show dependency tree
 
Reported: 2011-12-08 15:49 EST by Brian de Alwis CLA
Modified: 2015-11-13 16:15 EST (History)
3 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 Brian de Alwis CLA 2011-12-08 15:49:53 EST 
If you open an E3.x app (like Eclipse IDE) that uses the LegacyIDE.e4xmi (from org.eclipse.platform or org.eclipse.ui.workbench) in the background, Eclipse will appear to hang.  The contents will be populated once the window is activated.

The cause is that LegacyIDE.e4xmi only defines a window, but with no content; this is populated by an SWT.Activate event defined by WorkbenchSourceProvider's on the window's Shell.  I guess this listener is often installed after the window has already been opened.

It's a bit disconcerting to see (just happened to me again).

Steps to repeat:
1. Start an Eclipse app, and switch to a different app
2. Watch the shell come up, but the content will not be populated. (and notice that its title is Eclipse SDK)
3. Click into the shell or switch focus to the shell.  The contents will be populated.


My thoughts were that the LegacyIDE.e4xmi shouldn't have any windows defined, and the workbench should create and populate one as required.  This would also alleviate having the "Eclipse SDK" title in the window.
Comment 1 Remy Suen CLA 2011-12-14 15:38:09 EST 
If we go ahead with this, the generated window should have some reasonable default width. See bug 366114.
Comment 2 Brian de Alwis CLA 2015-11-13 16:15:20 EST 
This seems to have been fixed at some point.