Community
Participate
Working Groups
This bug was first reported in bug 367105 comment #10. The reported test case was to have breakpoints view cleared then populated with content repeatedly until exception occurred.
Hi Mike, I tried to populate/clear breakpoints view by adding bps individually, then using remove-all. I also tried switching between views, since this internally clears the view too. I haven't had luck reproducing it, do you have more details on how I could trip it?
(In reply to comment #1) > Hi Mike, > I tried to populate/clear breakpoints view by adding bps individually, then > using remove-all. I also tried switching between views, since this internally > clears the view too. I haven't had luck reproducing it, do you have more > details on how I could trip it? None. I have had no luck reproducing (locally) it either. I did notice that the JDT debug test suite had caused it during a build a few days ago.
Pasting the stacktrace here so that this bug can be found directly in bugzilla. Unfortunately, I don't have steps. I just found it in the log after I launched a runtime Eclipse. Variable view was visible, but Debug view wasn't. No breakpoints. org.eclipse.core.runtime.AssertionFailedException: assertion failed: Ignoring unexpected call to IWorkbenchSiteProgressService.decrementBusy(). This might be due to an earlier call to this method. at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110) at org.eclipse.ui.internal.progress.WorkbenchSiteProgressService.decrementBusy(WorkbenchSiteProgressService.java:423) at org.eclipse.debug.internal.ui.views.launch.LaunchView.viewerUpdatesComplete(LaunchView.java:1485) at org.eclipse.debug.internal.ui.viewers.model.TreeModelContentProvider$4.run(TreeModelContentProvider.java:720) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.debug.internal.ui.viewers.model.TreeModelContentProvider.notifyUpdate(TreeModelContentProvider.java:713) at org.eclipse.debug.internal.ui.viewers.model.TreeModelContentProvider.access$4(TreeModelContentProvider.java:708) at org.eclipse.debug.internal.ui.viewers.model.TreeModelContentProvider$3.run(TreeModelContentProvider.java:682) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4140) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) 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:352) 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:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:624) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:579) at org.eclipse.equinox.launcher.Main.run(Main.java:1433) at org.eclipse.equinox.launcher.Main.main(Main.java:1409)
We've fixed a number of out of order notification problems in bug 373790. If this issue is observed again, we can reopen it.
