Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 358229 - [Workbench] Errors encountered when opening a new workbench window should not prevent Eclipse shutdown
Summary: [Workbench] Errors encountered when opening a new workbench window should not...
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.8   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-20 08:19 EDT by Remy Suen CLA
Modified: 2020-01-23 14:12 EST (History)
0 users

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 Remy Suen CLA 2011-09-20 08:19:51 EDT 
Copied from bug 358119 comment 5.

---------------

I20110915-1308

1. Start in a new workspace.
2. Close the 'Welcome' screen.
3. Window > Save Perspective As... > Some name > OK
4. Window > New Window
5. Nothing happens, the error is logged, check the 'Error Log' view.
6. Close your window.
7. Eclipse will _not_ prompt you.
8. Check your processes, Eclipse is actually still running. If you try to run Eclipse again it will tell you the workspace is still in use.
Comment 1 Eric Moffatt CLA 2011-10-18 15:40:33 EDT 
Remy, is this 3.x or 4.x (or both), the 'Close Welcome...' is leading me to believe it's 3.x...
Comment 2 Remy Suen CLA 2011-10-18 16:06:13 EDT 
(In reply to comment #1)
> Remy, is this 3.x or 4.x (or both), the 'Close Welcome...' is leading me to
> believe it's 3.x...

This is a 3.x problem. We need code in our workbench window creation to ensure that exceptions do not cause it to remain in our list of opened workbench windows.
Comment 3 Eclipse Genie CLA 2020-01-23 14:12:40 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.