Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 138102

Summary: Eclipse fails to start after plug-in change
Product: [Eclipse Project] Platform Reporter: Ed Willink <ed>
Component: ResourcesAssignee: Platform-Resources-Inbox <platform-resources-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: major    
Priority: P3 CC: pascal, sptaszkiewicz
Version: 3.2   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:
Attachments:
Description Flags
.log file for original report none

Description Ed Willink CLA 2006-04-22 08:18:55 EDT 
Inappropriate plug-in configurations can leave a Workspace almost fatally broken. This has now happened to me twice. Once when upgrading from 3.2M5 to 3.2M6 and again after switching EMFT OCL.

I had a viable 3.2M6 workspace with EMF 2.2.0M6 and EMFT 1.0.0RC1. I had EMFT
OCL loaded as a project (since an internal jar library must be unnested to run unit tests.) I closed the EMFT OCL project preparatory to creating an update site for my project, since I have found that builds against a projhect rather than plugin cause unusable plugins. I neglected to rebuild all before closing Eclipse. I cannot open my workspace again; I am just directed to the .log file which I will attach in a further comment if Bugzilla lets me.

The .log quite clearly shows some unhealthy plugin references, but I need toi be able to start Eclipse in order to solve the problems!

Not being able to start Eclipse is not satisfactory. Problem plugions must be disable to ensure startup at all times.
Comment 1 Ed Willink CLA 2006-04-22 08:19:52 EDT 
Created attachment 39238 [details]
.log file for original report
Comment 2 Pascal Rapicault CLA 2006-04-24 09:37:26 EDT 
Can you give detailed steps on how to reproduce this problem?
Comment 3 John Arthorne CLA 2006-04-24 12:39:16 EDT 
It looks like the root cause is:

Caused by: java.lang.OutOfMemoryError: Java heap space
Root exception:
java.lang.OutOfMemoryError: Java heap space

And we are not recovering properly from this on the next startup. I recommend starting with more Java heap, such as:

eclipse -vmargs -Xmx300M
Comment 4 Ed Willink CLA 2006-04-24 15:27:36 EDT 
No.

I think the out of memory comes from my build source plug-in launch configuration, which uses ANT and so leaks monstrously. I can usually do
about two source builds before an out of memory.

I'm already on -Xmx512M.

My compliant is not about the crash, though that's sad. It's about the
inability to restart, when memory size should not be an issue anyway.

Eclipse must do a best attempt to start up.

I had to spend some time pruning .metadata to get things restartable.
It's a rubbish org.eclipse.resources/.root or .safetable that prevents
start up.
Comment 5 Szymon Ptaszkiewicz CLA 2011-01-04 07:12:43 EST 

*** This bug has been marked as a duplicate of bug 149121 ***