Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 288261

Summary:	Unhandled event loop exception
Product:	[Eclipse Project] JDT	Reporter:	Lysathor <lysathor>
Component:	APT	Assignee:	Lysathor <lysathor>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	eclipse, knut.wannheden, remy.suen
Version:	3.5
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Lysathor

2009-09-01 10:14:00 EDT

eclipse.buildId=I20090611-1540
java.version=1.6.0_16
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
Framework arguments:  -product org.eclipse.epp.package.java.product
Command-line arguments:  -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.java.product


Error
Tue Sep 01 08:13:17 CEST 2009
Unhandled event loop exception

org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.swt.SWTException: Widget is disposed)
at org.eclipse.swt.SWT.error(SWT.java:3884)
at org.eclipse.swt.SWT.error(SWT.java:3799)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:137)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3855)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3476)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369)
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(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:559)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)
at org.eclipse.equinox.launcher.Main.run(Main.java:1311)
Caused by: org.eclipse.swt.SWTException: Widget is disposed
at org.eclipse.swt.SWT.error(SWT.java:3884)
at org.eclipse.swt.SWT.error(SWT.java:3799)
at org.eclipse.swt.SWT.error(SWT.java:3770)
at org.eclipse.swt.widgets.Widget.error(Widget.java:463)
at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:336)
at org.eclipse.swt.widgets.Control.update(Control.java:3799)
at org.eclipse.jface.layout.TreeColumnLayout$1.run(TreeColumnLayout.java:57)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
... 22 more




-- Configuration Details --
Product: Eclipse 1.2.0.20090619-0620 (org.eclipse.epp.package.java.product)
Installed Features:
 org.eclipse.jdt 3.5.0.v20090527-2000-7r88FEeFJePyvYeA33DjZ_c1

Comment 1 Walter Harley

2009-09-01 10:22:10 EDT

This has nothing whatsoever to do with JDT annotation processing, as far as I can tell.  Before I reassign it to the correct product and component, can you tell me how come you ended up with the classification you did?  Did you go through the web site, or some other bug entry tool?

Comment 2 Lysathor

2009-09-01 15:39:34 EDT

I just created the bug report via eclipse help menu. I did not select something special. I have not intended to select "JDT annotation processing". I do not know the abbreviations, so I let the default setting eclipse presented (e.g. JDT, APT)

Comment 3 Walter Harley

2009-09-02 00:24:35 EDT

Thanks, that's quite helpful.  One more question: what Eclipse package are you using?  (Classic, J2EE, Java, ... ?)

Comment 4 Remy Suen

2009-09-02 07:54:35 EDT

(In reply to comment #3)
> Thanks, that's quite helpful.  One more question: what Eclipse package are you
> using?  (Classic, J2EE, Java, ... ?)

(In reply to comment #0)
> -product org.eclipse.epp.package.java.product

Looks like the standard Java package to me. I guess Mylyn's defaults are bad or it should "guess" better.

Lysanthor, your logs indicate an error with some tree columns. What were you doing when you got the error?

Comment 5 Lysathor

2009-09-02 08:07:00 EDT

The eclipse edition is the standard edition for java (3.5). I assumed that eclipse would fill in the correct versions by itself (I created the bug report via help menu of eclipse). I am a bit surprised that questions regarding eclips version arise, the information provided by eclipse should cover that.

I cannot remember excactly what I did. I think the problems occured directly after starting a debug session of my project application. But after exiting the project application and restarting it (eclipse still running), the problem did not exist any more. Seems to be sporadic.

Comment 6 Lysathor

2009-09-02 08:09:48 EDT

According to tree columns: My code adjusts the width of table columns (I do not know, what tree columns are). According to the stack trace it is an eclipse internal class (jface.layout.TreeColumnLayout).

Comment 7 Knut Wannheden

2012-12-05 06:25:53 EST

I just ran into the same "Widget is disposed" exception in the context of an SWTBot test. AFAICT the problem is that TreeColumnLayout doesn't check if the tree has been disposed within its Runnable posted to Display#asyncExec().

So I think this issue should be moved to Platform.SWT. Or should I report a new issue there?

Comment 8 Walter Harley

2012-12-05 21:03:28 EST

Please report a new issue there.  This bug's 3 years old and doesn't contain a lot of useful info at this point.  Thanks.

Comment 9 Knut Wannheden

2012-12-06 02:51:44 EST

Makes sense. I've now reported this as bug 395890. So I assume this bug can be closed now.

Comment 10 Walter Harley

2012-12-06 12:41:51 EST

Yep. Thanks for doing that.

*** This bug has been marked as a duplicate of bug 395890 ***