Community
Participate
Working Groups
Build Identifier: 20100218-1602 When I started my eclipse (3.5.2 based) today, the package explorer did not open properly. Instead it shows; org.eclipse.core.runtime.AssertionFailedException: null argument: at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85) at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73) at org.eclipse.jdt.internal.ui.workingsets.WorkingSetModel.<init>(WorkingSetModel.java:247) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$9.handleException(PackageExplorerPart.java:1446) at org.eclipse.core.runtime.SafeRunner.handleException(SafeRunner.java:75) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:44) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart.createWorkingSetModel(PackageExplorerPart.java:1441) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart.init(PackageExplorerPart.java:388) at org.eclipse.ui.internal.ViewReference.createPartHelper(ViewReference.java:340) at org.eclipse.ui.internal.ViewReference.createPart(ViewReference.java:226) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595) at org.eclipse.ui.internal.WorkbenchPage$ActivationList.setActive(WorkbenchPage.java:4212) at org.eclipse.ui.internal.WorkbenchPage$18.runWithException(WorkbenchPage.java:3271) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3885) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3506) at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803) at org.eclipse.ui.internal.Workbench$28.runWithException(Workbench.java:1384) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3885) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3506) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2316) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) Closing and re-opening the view gave me a working view. Restarting eclipse after this also gave me a working view Reproducible: Couldn't Reproduce
Moving to JDT UI
Can you please attach the full .log? Markus, it fails on the fallback code you added a while back, see bug 173031.
Unfortunately the log file has long since gone.
I couldn't reproduce this, and I don't see how it could happen. I manually screwed the stored memento, but that only gave me the expected exception when restore failed, and the fallback worked properly. > Markus, it fails on the fallback code you added a while back, see bug 173031. Bug 173031 cleaned up that code, but the exception handling and fallback code didn't really change. Closing for now, please reopen if you see this again.
Created attachment 179388 [details] Error log from an Eclipse 3.6 installation Today I've come across the same error on an eclipse 3.6 install. I've attached the log file messages from today's start up. There appear to be lots of messages along the lines of "timed out waiting (5000ms) for thread". This appears to happen regularly, where-as I've only had the view part initialisation fail twice. I haven't used this workspace for a few days, but I believe last time I had it open, my laptop ran out of power before closing it - so there would have been an unclean shutdown.
Re-opening due to Comment #5
Simon, thanks for reporting back. The problem is not in the WorkingSetModel. What we see is just a follow up exception due to forced loading and hence not fully initializing some classes. This can happen if two threads are loading the same class/bundle at the same time or if a bundle takes very long to start. The key question is which classes/threads are causing this. Can you reproduce the problem, e.g. by killing your Eclipse and restarting? If so, please take some stack dumps while starting. This should give use more details.
We can't do much without steps to reproduce the problem.
Hi, just had this again - but this time I had shutdown eclipse first (rather than it crashing out). This is a indigo based install on a different machine. Unfortunately I've not been able to reproduce this reliably so I've not been able to grab stack traces when the situation occurs.
*** Bug 391117 has been marked as a duplicate of this bug. ***
