Community
Participate
Working Groups
I20040112-1200, GTK+ 2.4.9, KDE 3.3.1, Linux 2.6.9 Clicking on the drop-down menu part of "Synchronize CVS" tool item (in the "Synchronize" view) leads to a "Widget is disposed" exception. This exception does not always happened, but seems to be timing related (not reproducible) and tied to switching perspectives. Once in this state, restarting Eclipse seems to be the only way to get back to a sane state. My workbench window layout is a bit peculiar, so I'll describe it. Recently, I've been playing with detached windows. As such, I have several views pulled out of the workbench window. The "Synchronize" view, for example, is a detached window. I was switching between the Java perspective and the Team Synchronizing perspective. Both perspectives have detached windows. The Synchronize view is only open in the Team Synchronizing perspective. The exception is as follows: org.eclipse.swt.SWTException: Widget is disposed at org.eclipse.swt.SWT.error(SWT.java:2827) at org.eclipse.swt.SWT.error(SWT.java:2752) at org.eclipse.swt.SWT.error(SWT.java:2723) at org.eclipse.swt.widgets.Widget.error(Widget.java:392) at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:328) at org.eclipse.swt.widgets.Menu.setLocation(Menu.java:816) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:537) at org.eclipse.jface.action.ActionContributionItem.access$2 (ActionContributionItem.java:505) at org.eclipse.jface.action.ActionContributionItem$7.handleEvent(ActionContributionItem.java:460) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:82) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1002) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2718) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2417) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1577) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1543) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:287) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:144) at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:102) at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:220) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:274) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:129) 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:582) at org.eclipse.core.launcher.Main.basicRun(Main.java:185) at org.eclipse.core.launcher.Main.run(Main.java:684) at org.eclipse.core.launcher.Main.main(Main.java:668)
Can you reproduce this with any other dropdown view menu? Search has one...
I have only seen this the one time.
Not sure where to punt this... I seem recall a similar problem with dropdown items with regards to detached views in the past...
I have seen this once or twice with no clear way to reproduce. However, I believe I may have a reproducible case now. Unfortunately, I'm not sure how many of the steps below are really necessary. Let me know if these steps work for you: 1.) Switch to the Java perspective. 2.) Create 3 detached views: (i) Javadoc (ii) Package Explorer, Hierarchy, Outline (iii) Problems, Search, Console, CVS Resource History 3.) Create two fast views: (i) JUnit (ii) Progress 4.) Close all other views and all editors. 5.) Switch to the Team Synchronizing perspective. 6.) Create 2 detached views: (i) Synchronize (make sure it contains a synchronization of some sort) (ii) Tasks, Problems, Console 7.) Create 2 fast views: (i) Progress (ii) CVS Resource History 8.) Close all other views and all editors. 9.) Switch back to the Java perspective. 10.) Open "IWorkbenchPart" in the Hierarchy view. 11.) Restart Eclipse. 12.) Switch to the Team Synchronizing perspective. At this point, Eclipse is hosed. There are "widget is disposed" exceptions when you try to do pretty much anything. To restore sanity, Eclipse must be restarted. I'm debating whether this should be upgraded to "Major"....
Has anyone experienced this recently?
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
