Comment 1 Jed Anderson 2002-08-19 16:05:42 EDT

Full post from the newsgroup:

I am using the 2.0 release and have a problem that won't go away. 
About
every minute or so eclipse will pegged my CPU to 100% for about 5 or 10
seconds. The only 
clue I have uncovered is a 14MB (!) .log file that is
full of messages that look like 
this:

!ENTRY org.eclipse.jdt.core 4 4 Aug 15, 2002 16:30:20.965
!MESSAGE Background 
Indexer Crash Recovery
!STACK 
0
java.lang.ArrayIndexOutOfBoundsException
	at
org.eclipse.jdt.internal.core.search.indexing.BinaryIndexer.extractType(BinaryIndexer.java:423)
	at
org.eclipse.jdt.internal.core.search.indexing.BinaryIndexer.extractReferenceFromConstantPool(BinaryIndexer.java:405)
	at
org.eclipse.jdt.internal.core.search.indexing.BinaryIndexer.indexClassFile(BinaryIndexer.java:510)
	at
org.eclipse.jdt.internal.core.search.indexing.BinaryIndexer.indexFile(BinaryIndexer.java:521)
	at
org.eclipse.jdt.internal.core.search.indexing.AbstractIndexer.index(AbstractIndexer.java:558)
	at 
org.eclipse.jdt.internal.core.index.impl.Index.add(Index.java:101)
	at
org.eclipse.jdt.internal.core.search.indexing.AddClassFileToIndex.execute(AddClassFileToIndex.java:55)
	at
org.eclipse.jdt.internal.core.search.processing.JobManager.run(JobManager.java:327)
	at 
java.lang.Thread.run(Thread.java:479)


If anyone can tell me how to remedy this, I would 
be very grateful.
Brian

Comment 2 Jed Anderson 2002-08-19 16:07:42 EDT

The original author was:
brian_vosburgh@yahoo.com

The original name of the post was "cpu 
spikes" and was sent on 8/15/2002 at 5:10 PM.

Comment 3 Brian Vosburgh 2002-08-20 14:11:06 EDT

I have a project that has a "Java Build Path" that includes a number 
of "External JARs" and a number of "class folders". One of the class folders 
(FOO) points to non-.class file resources that are used during testing (e.g. 
test data). I have found that this bug occurs when I start up eclipse; but if I 
simply move the class folder FOO somewhere else (e.g. my desktop), wait a few 
minutes for the CPU spikes to disappear, then move the folder back to its 
propert place, and the CPU spikes will not re-appear until I restart eclipse.

Comment 4 Kent Johnson 2002-10-02 11:14:11 EDT

Sorry this seems to have been lost in the PR bucket...

Brian did you get around this problem?

We're reimplementing the indexer so if you have, I would like to downgrade this 
PR.

Comment 5 Brian Vosburgh 2002-10-03 09:18:15 EDT

Actually, now that you mention it, the problem seems to have gone away with 
2.0.1. Sorry I did not say anything earlier. :-(

Comment 6 Kent Johnson 2002-10-03 12:31:24 EDT

Reported as fixed in 2.0.1.