Bug 1749 - Debugger did not show source for type, and generated "Failed to execute runnable" (1GL2VMQ)
Summary: Debugger did not show source for type, and generated "Failed to execute runna...
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 2.0   Edit
Hardware: All Windows 2000
: P1 critical (vote)
Target Milestone: ---   Edit
Assignee: Kai-Uwe Maetzel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-10 22:18 EDT by Nick Edgar CLA
Modified: 2001-12-03 06:42 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Edgar CLA 2001-10-10 22:18:40 EDT
There are two problems here:
problem 1:
- ran target eclipse under debugger (also a 202a install, plus changes to org.eclipse.ui)
- set breakpoint in Action.run() (actually it was in a new method run(Event), but this should reproduce it)
- in Java perspective in target eclipse, hit Create a Java Project button on toolbar
- breakpoint was hit (in WWinPluginAction(PluginAction).run(), so it was showing source for PluginAction.java).
- stepped through it until it called the delegate (delegate.run(this))
- stack frame was added: OpenProjectWizardAction(AbstractOpenWizardAction).run(IAction)
- source did not change: still showing PluginAction.java
- Open On / Declaring Type or Receiving Type had no effect, either on this stack frame or previous one, but did on earlier ones

problem 2:
- tried clicking down in lower stack frames, in rapid succession to see if other frames were OK
- got a "Failed to execute runnable" error dialog
- log had:
Log: Thu Oct 04 11:21:04 EDT 2001
1 org.eclipse.core.resources 4 Unhandled exception caught in event loop.
Log: Thu Oct 04 11:21:04 EDT 2001
4 org.eclipse.ui 0 Failed to execute runnable
org.eclipse.swt.SWTException: Failed to execute runnable
	at org.eclipse.swt.SWT.error(SWT.java:1817)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java(Compiled Code))
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java(Compiled Code))
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java(Compiled Code))
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java(Compiled Code))
	at org.eclipse.ui.internal.Workbench.run(Workbench.java:658)
	at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:820)
	at org.eclipse.core.boot.BootLoader.run(BootLoader.java:285)
	at java.lang.reflect.Method.invoke(Native Method)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:151)
	at org.eclipse.core.launcher.Main.run(Main.java:433)
	at org.eclipse.core.launcher.Main.main(Main.java:306)
Log: Thu Oct 04 11:21:04 EDT 2001
4 org.eclipse.core.runtime 0 Unhandled exception caught in event loop.
org.eclipse.swt.SWTException: Failed to execute runnable
	at org.eclipse.swt.SWT.error(SWT.java:1817)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java(Compiled Code))
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java(Compiled Code))
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java(Compiled Code))
	at org.eclipse.jface.window.Window.runEventLoop(Window.java(Compiled Code))
	at org.eclipse.jface.window.Window.open(Window.java:523)
	at org.eclipse.jface.dialogs.MessageDialog.openError(MessageDialog.java:318)
	at org.eclipse.ui.internal.Workbench.handleExceptionInEventLoop(Workbench.java:362)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java(Compiled Code))
	at org.eclipse.ui.internal.Workbench.run(Workbench.java:658)
	at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:820)
	at org.eclipse.core.boot.BootLoader.run(BootLoader.java:285)
	at java.lang.reflect.Method.invoke(Native Method)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:151)
	at org.eclipse.core.launcher.Main.run(Main.java:433)
	at org.eclipse.core.launcher.Main.main(Main.java:306)
Log: Thu Oct 04 11:21:04 EDT 2001
4 org.eclipse.core.runtime 0 Failed to execute runnable
org.eclipse.swt.SWTException: Failed to execute runnable
	at org.eclipse.swt.SWT.error(SWT.java:1817)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java(Compiled Code))
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java(Compiled Code))
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java(Compiled Code))
	at org.eclipse.jface.window.Window.runEventLoop(Window.java(Compiled Code))
	at org.eclipse.jface.window.Window.open(Window.java:523)
	at org.eclipse.jface.dialogs.MessageDialog.openError(MessageDialog.java:318)
	at org.eclipse.ui.internal.Workbench.handleExceptionInEventLoop(Workbench.java:362)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java(Compiled Code))
	at org.eclipse.ui.internal.Workbench.run(Workbench.java:658)
	at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoader.java:820)
	at org.eclipse.core.boot.BootLoader.run(BootLoader.java:285)
	at java.lang.reflect.Method.invoke(Native Method)
	at org.eclipse.core.launcher.Main.basicRun(Main.java:151)
	at org.eclipse.core.launcher.Main.run(Main.java:433)
	at org.eclipse.core.launcher.Main.main(Main.java:306)

This seems to indicate a threading problem.

NOTES:
Comment 1 DJ Houghton CLA 2001-10-24 06:39:49 EDT
PRODUCT VERSION:
202a

Comment 2 Darin Swanson CLA 2001-11-30 12:22:09 EST
I could not reproduce problem #1.

Problem #2 was reproducable by rapidly clicking between stack frames that are 
from different compilation units (resulting in JavaEditors opening and closing 
rapidly).

The failed runnable:
Unhandled exception caught in event loop.
Reason:
Failed to execute runnable (java.lang.NullPointerException)
java.lang.NullPointerException
        at org.eclipse.ui.texteditor.AbstractTextEditor.getCursorPosition(Abstra
ctTextEditor.java:2172)
        at org.eclipse.ui.texteditor.AbstractTextEditor.updateStatusField(Abstra
ctTextEditor.java:2150)
        at org.eclipse.ui.texteditor.AbstractTextEditor.handleCursorPositionChan
ged(AbstractTextEditor.java:2130)
        at org.eclipse.ui.texteditor.AbstractTextEditor$5.run(AbstractTextEditor
.java:779)
        at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:29)
        at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.ja
va:93)
        at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:1345)
        at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:1173)
        at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:781)
        at org.eclipse.ui.internal.Workbench.run(Workbench.java:764)
        at org.eclipse.core.internal.boot.InternalBootLoader.run(InternalBootLoa
der.java:820)
        at org.eclipse.core.boot.BootLoader.run(BootLoader.java:285)
        at java.lang.reflect.Method.invoke(Native Method)
        at org.eclipse.core.launcher.Main.basicRun(Main.java:151)
        at org.eclipse.core.launcher.Main.run(Main.java:502)
        at org.eclipse.core.launcher.Main.main(Main.java:362)

Looks like the AbstractTextEditor is attempting a runnable after it is disposed.
Moving to Platform UI.
Comment 3 Nick Edgar CLA 2001-11-30 14:11:46 EST
Kai, could you please take a look at this.
Comment 4 Nick Edgar CLA 2001-11-30 15:20:24 EST
This is high priority for the debug team.
It causes eclipse to crash in such a way that metadata corrupted and 
unrecoverable.
Comment 5 Kai-Uwe Maetzel CLA 2001-12-03 06:42:02 EST
Introduced guard code for all async exec. Build > 20011204.