Bug 188706

Summary:	[Change Sets] ConcurrentModificationException in changeset content provider
Product:	[Eclipse Project] Platform	Reporter:	Eugene Kuleshov <ekuleshov>
Component:	CVS	Assignee:	platform-cvs-inbox <platform-cvs-inbox>
Status:	ASSIGNED ---	QA Contact:
Severity:	normal
Priority:	P3
Version:	3.3
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Eugene Kuleshov

2007-05-23 13:59:34 EDT

Got this in the error log. Running Eclipse 3.3RC1

-- Error Log --
Date: Wed May 23 13:55:00 EDT 2007
Message: Unhandled event loop exception
Severity: Error
Plugin ID: org.eclipse.ui
Stack Trace:
org.eclipse.swt.SWTException: Failed to execute runnable (java.util.ConcurrentModificationException)
	at org.eclipse.swt.SWT.error(SWT.java:3547)
	at org.eclipse.swt.SWT.error(SWT.java:3465)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:126)
	at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3650)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3287)
	at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389)
	at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353)
	at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219)
	at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289)
	at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461)
	at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
	at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106)
	at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:153)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106)
	at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363)
	at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176)
	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:497)
	at org.eclipse.equinox.launcher.Main.basicRun(Main.java:436)
	at org.eclipse.equinox.launcher.Main.run(Main.java:1162)
	at org.eclipse.equinox.launcher.Main.main(Main.java:1137)
Caused by: java.util.ConcurrentModificationException
	at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)
	at java.util.HashMap$KeyIterator.next(HashMap.java:827)
	at org.eclipse.team.internal.core.subscribers.DiffTreeStatistics.countFor(DiffTreeStatistics.java:75)
	at org.eclipse.team.core.diff.provider.DiffTree.countFor(DiffTree.java:340)
	at org.eclipse.team.internal.ccvs.ui.mappings.ChangeSetContentProvider.hasIncomingChanges(ChangeSetContentProvider.java:456)
	at org.eclipse.team.internal.ccvs.ui.mappings.ChangeSetContentProvider.isVisibleInMode(ChangeSetContentProvider.java:443)
	at org.eclipse.team.internal.ccvs.ui.mappings.ChangeSetContentProvider.hasChildren(ChangeSetContentProvider.java:511)
	at org.eclipse.team.internal.ccvs.ui.mappings.ChangeSetContentProvider$2.run(ChangeSetContentProvider.java:273)
	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
	at org.eclipse.team.internal.ui.Utils$5.run(Utils.java:786)
	at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
	at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
	... 23 more

Comment 1 Michael Valenta

2007-05-23 14:38:01 EDT

Given that this code hasn't changed in ages and this is the first reported case of this, I think the fix can wait until 3.4.

Comment 2 Szymon Brandys

2008-05-09 04:23:13 EDT

Mass update - removing 3.4 target. This was one of the bugs marked for
investigation (and potential fixing) in 3.4 but we ran out of time. Please ping
on the bug if fixing it would be really important for 3.4, and does not require
API changes or feature work.

Comment 3 Eclipse Webmaster

2019-09-06 16:07:42 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.