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

Bug 342976

Summary:	[frame sync] ArrayIndexOutOfBoundsException while UI children update
Product:	[Eclipse Project] JDT	Reporter:	Patric Rufflar <patric>
Component:	Debug	Assignee:	JDT-Debug-Inbox <jdt-debug-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	Michael_Rennie
Version:	3.7	Keywords:	needinfo
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug
Bug Depends on:
Bug Blocks:	342974

Description Patric Rufflar

2011-04-15 09:58:12 EDT

Build Identifier: 3.6.2

Error log states "An internal error occurred during: "children update"."

java.lang.ArrayIndexOutOfBoundsException: 10
at java.util.ArrayList.add(ArrayList.java:352)
at org.eclipse.jdt.internal.debug.ui.monitors.JavaMonitor.addElement(JavaMonitor.java:214)
at org.eclipse.jdt.internal.debug.ui.monitors.JavaContendedMonitor.<init>(JavaContendedMonitor.java:50)
at org.eclipse.jdt.internal.debug.ui.monitors.JavaOwningThread.getContendedMonitor(JavaOwningThread.java:74)
at org.eclipse.jdt.internal.debug.ui.monitors.JavaMonitorThread.getContendedMonitor(JavaMonitorThread.java:128)
at org.eclipse.jdt.internal.debug.ui.monitors.ThreadMonitorManager.getContendedMonitor(ThreadMonitorManager.java:206)
at org.eclipse.jdt.debug.ui.JavaDebugUtils.getContendedMonitor(JavaDebugUtils.java:59)
at org.eclipse.jdt.internal.debug.ui.monitors.JavaThreadContentProvider.getChildren(JavaThreadContentProvider.java:88)
at org.eclipse.jdt.internal.debug.ui.monitors.JavaThreadContentProvider.getChildren(JavaThreadContentProvider.java:66)
at org.eclipse.debug.internal.ui.model.elements.ElementContentProvider.retrieveChildren(ElementContentProvider.java:87)
at org.eclipse.debug.internal.ui.model.elements.ElementContentProvider$1.run(ElementContentProvider.java:42)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Reproducible: Didn't try

Comment 1 Michael Rennie

2011-04-15 11:52:45 EDT

Do you have any other information? 

What were you doing when the exception occurred (stepping, resuming, etc)? What kind of launch was it? Do you have steps to reproduce the problem?

Comment 2 Michael Rennie

2011-04-19 11:11:29 EDT

Without further information I am unable to reproduce, but we could prevent this kind of error in the future by making the backing list synchronized since it can be accessed / modified from different threads.

Comment 3 Eclipse Genie

2019-08-22 17:50:40 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.

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.

--
The automated Eclipse Genie.