Bug 196314

Summary: ConcurrentModificationException during startup
Product: [Eclipse Project] JDT Reporter: Karsten Becker <eclipse>
Component: CoreAssignee: Jerome Lanneluc <jerome_lanneluc>
Status: VERIFIED WORKSFORME QA Contact:
Severity: normal    
Priority: P3    
Version: 3.3   
Target Milestone: 3.5 M1   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Karsten Becker CLA 2007-07-12 09:49:06 EDT
I got this stacktrace during starting another eclipse instance:

!ENTRY org.eclipse.core.resources 4 2 2007-07-12 15:41:15.625
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
!STACK 0
java.util.ConcurrentModificationException
	at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793)
	at java.util.HashMap$ValueIterator.next(HashMap.java:821)
	at org.eclipse.jdt.internal.core.DeltaProcessor.resourceChanged(DeltaProcessor.java:1876)
	at org.eclipse.jdt.internal.core.DeltaProcessingState.resourceChanged(DeltaProcessingState.java:368)
	at org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:282)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
	at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:276)
	at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:148)
	at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:311)
	at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1018)
	at org.eclipse.core.internal.resources.Resource.refreshLocal(Resource.java:1433)
	at org.eclipse.core.internal.refresh.RefreshJob.runInWorkspace(RefreshJob.java:141)
	at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Comment 1 Karsten Becker CLA 2007-07-12 09:50:11 EDT
Build was N20070705-0010
Comment 2 Jerome Lanneluc CLA 2007-12-04 05:40:51 EST
Sorry it took so long to respond. Have you seen this problem recently? Especially with an integration build. A nightly build is sometime not very stable. That could explain the exception.
Comment 3 Jerome Lanneluc CLA 2008-06-26 09:58:12 EDT
Please reopen if you have more information
Comment 4 Kent Johnson CLA 2008-08-06 14:40:45 EDT
Verified for 3.5M1 using I20080805-1307