Community
Participate
Working Groups
Build Identifier: I20110620-1631 Hello, please find attached the workspace that crashes Eclipse on startup. I had to move it away and create a new one to be able to work. KR, Grimeton Reproducible: Always Steps to Reproduce: 1. Start Eclipse 2. See it crash
Created attachment 203356 [details] Workspace that is crashing Eclipse
I just verified that the workspace refuses to load in Eclipse N20121027-2000 on Windows 7, even after blowing away org.eclipse.core.resources (where individual project info is stored). I suspect the error I get: Unable to load class 'org.eclipse.e4.ui.workbench.renderers.swt.cocoa.CloseDialogHandler' from bundle '67' is related to running on Windows, rather than OS X -- but looking in the log, I see various NullPointerExceptions. That would be probably a good place to look next. Oliver -- if you're still interested, please speak up.
It's not a crash, but looks like your workbench layout/config got corrupted: the org.eclipse.e4.ui.model.application.ui.MElementContainer.getChildren() returns 'null' for your workspace. You should be able to start your workspace after deleting the following file: .metadata\.plugins\org.eclipse.e4.workbench\workbench.xmi We can't do much if we don't have the steps to get to the corrupted workspace layout.
*** Bug 389738 has been marked as a duplicate of this bug. ***
I ran into what I believe is a similar issue a 2 months ago. It took me over an hour to chase it down. Deleting .metadata\.plugins\org.eclipse.e4.workbench that contains the workbench.xmi file fixed the problem for me. It happened again today and I deleted the same directory which allowed eclipse to start up. This was the entry in the .log reported as eclipse failed to get past the splash screen: !ENTRY org.eclipse.ui 4 0 2013-04-25 08:53:18.018 !MESSAGE Error occurred during status handling !STACK 0 java.lang.NullPointerException at org.eclipse.ui.internal.statushandlers.StatusHandlerRegistry.<init>(StatusHandlerRegistry.java:72) at org.eclipse.ui.internal.statushandlers.StatusHandlerRegistry.getDefault(StatusHandlerRegistry.java:91) at org.eclipse.ui.statushandlers.StatusManager.getStatusHandler(StatusManager.java:135) at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:189) at org.eclipse.ui.statushandlers.StatusManager.handle(StatusManager.java:231) at org.eclipse.ui.statushandlers.StatusManager$StatusManagerLogListener.logging(StatusManager.java:305) at org.eclipse.core.internal.runtime.RuntimeLog.logToListeners(RuntimeLog.java:160) at org.eclipse.core.internal.runtime.PlatformLogWriter.logged(PlatformLogWriter.java:100) at org.eclipse.equinox.log.internal.ExtendedLogReaderServiceFactory.safeLogged(ExtendedLogReaderServiceFactory.java:86) at org.eclipse.equinox.log.internal.ExtendedLogReaderServiceFactory.logPrivileged(ExtendedLogReaderServiceFactory.java:205) at org.eclipse.equinox.log.internal.ExtendedLogReaderServiceFactory.log(ExtendedLogReaderServiceFactory.java:178) at org.eclipse.equinox.log.internal.ExtendedLogServiceFactory.log(ExtendedLogServiceFactory.java:65) at org.eclipse.equinox.log.internal.ExtendedLogServiceImpl.log(ExtendedLogServiceImpl.java:87) at org.eclipse.equinox.log.internal.LoggerImpl.log(LoggerImpl.java:54) at org.eclipse.core.internal.runtime.PlatformLogWriter.logging(PlatformLogWriter.java:43) at org.eclipse.core.internal.runtime.RuntimeLog.log(RuntimeLog.java:96) at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:653) at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:71) I would not be able to reproduce, but I can give you some background: 1. I had eclipse up for a few days 2. The editor area became fairly unresponsive FYI: I looked in the Windows task manager and noticed that the working set had gotten quite large: 880MB, the User Objects: 9,999. After deleting the xmi file and restarting eclipse these numbers are 101MB and 529. 3. I tried to close some editors until the editor tab area became unresponsive and then closed eclipse. 4. I restarted eclipse and ran into this problem. Workaround: Delete the xmi file Bad news: I lost the configuration of the perspective, layout of views, open editors, ...
I can reproduce the problem after getting into the stack overflow from bug 404873 and then exiting: afterwards I can no longer start Eclipse. Fixing said bug also fixes this issue. *** This bug has been marked as a duplicate of bug 404873 ***
