Bug 122243 - Background indexer crashes
Summary: Background indexer crashes
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1.1   Edit
Hardware: PC Windows XP
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2005-12-28 07:27 EST by John-Michael Feist CLA
Modified: 2009-08-30 02:06 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John-Michael Feist CLA 2005-12-28 07:27:25 EST 
The "Open Type" dialog shows only about 10 classes out of mor than 10000 files to index and the following entry appears in the logfile:

!MESSAGE Background Indexer Crash Recovery
!STACK 0
java.lang.ArrayIndexOutOfBoundsException: 1883
	at org.eclipse.jdt.internal.core.search.indexing.BinaryIndexer.extractName(BinaryIndexer.java:374)
	at org.eclipse.jdt.internal.core.search.indexing.BinaryIndexer.extractReferenceFromConstantPool(BinaryIndexer.java:407)
	at org.eclipse.jdt.internal.core.search.indexing.BinaryIndexer.indexDocument(BinaryIndexer.java:536)
	at org.eclipse.jdt.internal.core.search.JavaSearchParticipant.indexDocument(JavaSearchParticipant.java:74)
	at org.eclipse.jdt.internal.core.search.indexing.IndexManager.indexDocument(IndexManager.java:290)
	at org.eclipse.jdt.internal.core.search.indexing.IndexManager$1.execute(IndexManager.java:601)
	at org.eclipse.jdt.internal.core.search.processing.JobManager.run(JobManager.java:372)
	at java.lang.Thread.run(Unknown Source)


Immediately after having cleaned all projects, the type list seems to be complete, but less than one minute later, the same crash occurs again and the type list is reduced as before.
The same behaviour can be observed in Eclipse 3.1 .
The problem seems to appear only if projects containing already compiled class files (without the corresponding sources) are open.
Comment 1 Olivier Thomann CLA 2005-12-28 14:09:04 EST 
Do you have obfuscated .class files?
Comment 2 John-Michael Feist CLA 2005-12-29 05:23:35 EST 
Looking at some samples, there seem to be no obfuscated class files.
Comment 3 Olivier Thomann CLA 2006-10-10 15:29:43 EDT 
If you could provide a test case, it would be great.
Or let us know if this still occurs with 3.2.1 or 3.3 integration builds.
Closing as REMIND.
Please reopen if you still get it with builds mentionned above.
Comment 4 Denis Roy CLA 2009-08-30 02:06:06 EDT 
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.