Community
Participate
Working Groups
I got into a state where performing an Open Types (CTRL-SHIRT-T) opens a "searching" dialog which never closes. I can cancel the dialog but it never completes the search normally. I am using 3.1 build I200409140800. I will attach the VM core dump which includes the VM information.
Created attachment 14578 [details] JVM stack traces
JDT Core doesn't appear in the stack traces. Moving to JDT UI to investigate why the AllTypeCache is hanging.
The problem is that the All types cache died due to an runtime exception (which is very likely caused by a bug in the VM you are using). Michael, can you please check if you find the stack trace of bug 73254 in your log. *** This bug has been marked as a duplicate of 73254 ***
The only error I see is the following. This may actually be a bug in our code (although the fact that it caused the allTypeCache to fail is definitely a VM bug). java.util.ConcurrentModificationException at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:462) at java.util.AbstractList$Itr.next(AbstractList.java:433) at org.eclipse.team.internal.ccvs.ui.subscriber.CommitSetManager.resourceSyncInfoC hanged(CommitSetManager.java:239) at org.eclipse.team.internal.ccvs.core.util.ResourceStateChangeListeners$1.notify (ResourceStateChangeListeners.java:97) at org.eclipse.team.internal.ccvs.core.util.ResourceStateChangeListeners$Notificat ion.run(ResourceStateChangeListeners.java:54) at org.eclipse.core.internal.runtime.InternalPlatform.run (InternalPlatform.java:615) at org.eclipse.core.runtime.Platform.run(Platform.java:747) at org.eclipse.team.internal.ccvs.core.util.ResourceStateChangeListeners$Notificat ion.run(ResourceStateChangeListeners.java:51) at org.eclipse.team.internal.ccvs.core.util.ResourceStateChangeListeners.fireNotif ication(ResourceStateChangeListeners.java:75) at org.eclipse.team.internal.ccvs.core.util.ResourceStateChangeListeners.resourceS yncInfoChanged(ResourceStateChangeListeners.java:95) at org.eclipse.team.internal.ccvs.core.resources.EclipseSynchronizer.broadcastReso urceStateChanges(EclipseSynchronizer.java:992) at org.eclipse.team.internal.ccvs.core.resources.EclipseSynchronizer.commitCache (EclipseSynchronizer.java:970) at org.eclipse.team.internal.ccvs.core.resources.EclipseSynchronizer$1.run (EclipseSynchronizer.java:498) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1674) at org.eclipse.team.internal.ccvs.core.resources.EclipseSynchronizer.flush (EclipseSynchronizer.java:496) at org.eclipse.team.internal.core.subscribers.BatchingLock$ThreadInfo.flush (BatchingLock.java:182) at org.eclipse.team.internal.ccvs.core.syncinfo.ReentrantLock$CVSThreadInfo.flush (ReentrantLock.java:53) at org.eclipse.team.internal.core.subscribers.BatchingLock$ThreadInfo.popRule (BatchingLock.java:114) at org.eclipse.team.internal.core.subscribers.BatchingLock.release (BatchingLock.java:309) at org.eclipse.team.internal.ccvs.core.resources.EclipseSynchronizer.endBatching (EclipseSynchronizer.java:479) at org.eclipse.team.internal.ccvs.core.resources.EclipseSynchronizer.run (EclipseSynchronizer.java:1384) at org.eclipse.team.internal.ccvs.ui.subscriber.CVSSubscriberOperation.run (CVSSubscriberOperation.java:67) at org.eclipse.team.internal.ui.actions.JobRunnableContext.run (JobRunnableContext.java:159) at org.eclipse.team.internal.ui.actions.JobRunnableContext$3.runInWorkspace (JobRunnableContext.java:179) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run (InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
Micheal, the exception happens in a thread different than the all types cache thread. So the thread shouldn't die because of this exception. The JVM trace you attached doesn't contain an all types thread anymore. So it must have died. I asked for the log to make sure that there aren't any other exceptions which are caused be a VM problem. Can you attach your whole log file.
Created attachment 14642 [details] Log file Here's the log file as requested
