Community
Participate
Working Groups
Just happend to me while starting up Eclipse. Will try to reproduce it. -- Error Details -- Date: Thu Jan 13 14:21:44 CET 2011 Message: Unhandled event loop exception Severity: Error Product: Eclipse SDK 3.7.0.v201008051700 (org.eclipse.sdk.ide) Plugin: org.eclipse.ui Exception Stack Trace: org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.core.runtime.AssertionFailedException: null argument:Notification handler has not been initialized) at org.eclipse.swt.SWT.error(SWT.java:4083) at org.eclipse.swt.SWT.error(SWT.java:3998) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:137) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3527) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3174) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) 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:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) Caused by: org.eclipse.core.runtime.AssertionFailedException: null argument:Notification handler has not been initialized at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85) at org.eclipse.mylyn.internal.commons.ui.notifications.NotificationService.notify(NotificationService.java:56) at org.eclipse.mylyn.internal.builds.ui.BuildNotifier.handle(BuildNotifier.java:41) at org.eclipse.mylyn.internal.builds.ui.BuildNotifier$1.doNotifyChanged(BuildNotifier.java:30) at org.eclipse.mylyn.internal.builds.ui.view.BuildModelContentAdapter.notifyChanged(BuildModelContentAdapter.java:37) at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:380) at org.eclipse.mylyn.builds.internal.core.BuildPlan.setStatus(BuildPlan.java:665) at org.eclipse.mylyn.builds.internal.core.BuildPlan.eSet(BuildPlan.java:922) at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eSet(BasicEObjectImpl.java:1081) at org.eclipse.emf.ecore.util.EcoreUtil$Copier.copyAttribute(EcoreUtil.java:621) at org.eclipse.mylyn.builds.internal.core.BuildPlan$1.copyAttribute(BuildPlan.java:1105) at org.eclipse.emf.ecore.util.EcoreUtil$Copier.copy(EcoreUtil.java:481) at org.eclipse.mylyn.builds.internal.core.BuildPlan.merge(BuildPlan.java:1113) at org.eclipse.mylyn.builds.internal.core.operations.RefreshSession.update(RefreshSession.java:172) at org.eclipse.mylyn.builds.internal.core.operations.RefreshSession$5.run(RefreshSession.java:160) at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:164) at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:158) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) ... 22 more
Created attachment 188116 [details] work around
Thanks Benjamin. I have committed the attached work-around for now to prevent the exception. I'll keep this open so we revisit this before the release to determine the cause.
I think we are good here. For some reason an event was being generated that did not have a registered handler but it seems okay to ignore it in this case.
