Bug 137610 - [Workbench] when restart is called twice Workbench should assert an error
Summary: [Workbench] when restart is called twice Workbench should assert an error
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P5 major (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2006-04-19 17:21 EDT by Michael Van Meekeren CLA
Modified: 2019-09-06 15:36 EDT (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 Michael Van Meekeren CLA 2006-04-19 17:21:33 EDT 
See bug 127137, there was a case where the workbench state was being saved twice and the second time (since Workbench.hardClose() was called) all windows were closed and bogus state was saved.  

We should throw an exception in this case.
Comment 1 Tod Creasey CLA 2007-06-18 16:29:00 EDT 
There are currently no plans to work on this although we would be happy to review a a patch.
Comment 2 Eclipse Webmaster CLA 2019-09-06 15:30:20 EDT 
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.

If you have further information on the current state of the bug, please add it. 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.
Comment 3 Eclipse Webmaster CLA 2019-09-06 15:36:34 EDT 
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.

If you have further information on the current state of the bug, please add it. 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.