Community
Participate
Working Groups
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.
Is this still an issue in 3.2?
Yes, this is almost certainly still an issue.
*** Bug 156486 has been marked as a duplicate of this bug. ***
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Remy is now responsible for watching the [EditorMgmt] component area.
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.
