Bug 72463

Summary:	[EditorMgmt] Crash on file load repeated on workspace restart
Product:	[Eclipse Project] Platform	Reporter:	Mike Capp <mike.capp>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	vlsergey
Version:	3.0
Target Milestone:	---
Hardware:	PC
OS:	Windows 2000
Whiteboard:

Description Mike Capp

2004-08-23 15:41:39 EDT

Problem is the following sequence of events:


1. Opening a file in an Eclipse editor causes a crash for whatever reason.

2. User restarts Eclipse.

3. Eclipse rereads old workspace on startup, including the crasher file.

4. Eclipse crashes again.

5. Rinse and repeat. User has no chance to fix the problem short of manually
editing the ".metadata\.plugins\org.eclipse.ui.workbench\workbench.xml" config
file. (Come to think of it, moving or renaming the crasher file would also
probably have worked; not sure why that didn't occur to me at the time.)


For a specific example, see Bug 70322 - the specific crash has apparently been
fixed, but probably not the broader issue. 

If possible, a newly opened file should not be added to the workspace's
persisted editor list until everything that could possibly go wrong with the
file open has succeeded. Or maybe Eclipse should offer to startup in "safe
mode", with no open editors, if it crashed on the previous run.

Comment 1 Tod Creasey

2006-04-15 14:28:35 EDT

Is this still an issue in 3.2?

Comment 2 Kim Horne

2006-04-15 14:58:16 EDT

Yes, this is almost certainly still an issue.

Comment 3 Kim Horne

2007-02-01 15:53:10 EST

*** Bug 156486 has been marked as a duplicate of this bug. ***

Comment 4 Susan McCourt

2009-07-09 19:06:09 EDT

As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009

Comment 5 Boris Bokowski

2009-11-17 13:04:35 EST

Remy is now responsible for watching the [EditorMgmt] component area.

Comment 6 Eclipse Webmaster

2019-09-06 16:14:32 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.