Bug 301801

Summary: Eclipse cannot start because Workspace apparently corrupted after a clean shutdown
Product: [Eclipse Project] Platform Reporter: Ed Randall <ed.randall>
Component: ResourcesAssignee: Platform-Resources-Inbox <platform-resources-inbox>
Status: NEW --- QA Contact: Szymon Brandys <Szymon.Brandys>
Severity: normal    
Priority: P3 CC: remy.suen
Version: 3.5.1   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
eclipse-workspace/.metadata/.log
none
Eclipse Installation Details / Configuration contents none

Description Ed Randall CLA 2010-02-04 05:36:08 EST 
Build Identifier: 20090920-1017

Eclipse refuses to start this morning apparently because the Workspace became corrupted ... but the shutdown last night was clean.

The simple dialog-box-of-last-resort appears:
An error has occurred.  See the log file...
.log file attached.

The install is not corrupted because it runs fine against my other workspaces.

Eclipse should be able to recover in these types of situation.



Reproducible: Didn't try
Comment 1 Ed Randall CLA 2010-02-04 05:37:04 EST 
Created attachment 158161 [details]
eclipse-workspace/.metadata/.log
Comment 2 Ed Randall CLA 2010-02-04 05:39:29 EST 
If I knew what file it was that is causing "java.io.UTFDataFormatException: malformed input around byte 22962" I could delete it and try again...
Comment 3 Ed Randall CLA 2010-02-04 06:28:29 EST 
If I delete the file
eclipse-workspace\.metadata\.plugins\org.eclipse.core.resources\.root\1.tree
then I can start it again, but have to re-import all projects - at least all
the other settings are preserved that way, as opposed to if I have to create a
whole new workspace.
Comment 4 Ed Randall CLA 2010-02-04 06:29:15 EST 
Created attachment 158165 [details]
Eclipse Installation Details / Configuration contents
Comment 5 Eclipse Webmaster CLA 2019-09-06 16:06:15 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.