Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 342974 - An exception occurred in asynchronous runnable
Summary: An exception occurred in asynchronous runnable
Status: CLOSED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on: 342976
Blocks:
  Show dependency tree
 
Reported: 2011-04-15 09:55 EDT by Patric Rufflar CLA
Modified: 2020-03-31 04:00 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Patric Rufflar CLA 2011-04-15 09:55:21 EDT 
Build Identifier: 3.6.2

error log text states "An exception occurred in asynchronous runnable."

java.lang.IllegalArgumentException: null source
at java.util.EventObject.<init>(EventObject.java:38)
at org.eclipse.debug.core.DebugEvent.<init>(DebugEvent.java:304)
at org.eclipse.jdt.internal.debug.ui.monitors.JavaMonitor.fireChangeEvent(JavaMonitor.java:190)
at org.eclipse.jdt.internal.debug.ui.monitors.JavaMonitor.update(JavaMonitor.java:177)
at org.eclipse.jdt.internal.debug.ui.monitors.JavaMonitor.refresh(JavaMonitor.java:218)
at org.eclipse.jdt.internal.debug.ui.monitors.JavaMonitorThread.refresh(JavaMonitorThread.java:286)
at org.eclipse.jdt.internal.debug.ui.monitors.ThreadMonitorManager$RefreshAndDetectDeadlock.run(ThreadMonitorManager.java:228)
at org.eclipse.debug.core.DebugPlugin$AsynchRunner.run(DebugPlugin.java:1048)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.debug.core.DebugPlugin$AsynchRunner.async(DebugPlugin.java:1031)
at org.eclipse.debug.core.DebugPlugin$EventDispatchJob.run(DebugPlugin.java:388)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Reproducible: Didn't try
Comment 1 Michael Rennie CLA 2011-04-15 12:10:01 EDT 
looks like it is caused by bug 342976, where a bogus value appears in the backing elements ArrayList
Comment 2 Eclipse Genie CLA 2020-03-31 04:00:52 EDT 
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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.