Bug 31013 - [infrastructure] npe in index crash recovery
Summary: [infrastructure] npe in index crash recovery
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 3.0 M8   Edit
Assignee: Kent Johnson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-05 14:30 EST by Adam Kiezun CLA
Modified: 2004-03-24 11:06 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Kiezun CLA 2003-02-05 14:30:48 EST
!ENTRY org.eclipse.jdt.core 4 4 Feb 05, 2003 20:03:07.71
!MESSAGE Background Indexer Crash Recovery
!STACK 0
java.lang.NullPointerException
	at org.eclipse.jdt.internal.core.index.impl.CodeByteStream.readUnary
(CodeByteStream.java:180)
	at org.eclipse.jdt.internal.core.index.impl.CodeByteStream.readGamma
(CodeByteStream.java:113)
	at 
org.eclipse.jdt.internal.core.index.impl.GammaCompressedIndexBlock.nextEntry
(GammaCompressedIndexBlock.java:96)
	at 
org.eclipse.jdt.internal.core.index.impl.BlocksIndexInput.moveToNextWordEntry
(BlocksIndexInput.java:186)
	at org.eclipse.jdt.internal.core.index.impl.MergeFactory.mergeReferences
(MergeFactory.java:176)
	at org.eclipse.jdt.internal.core.index.impl.MergeFactory.merge
(MergeFactory.java:85)
	at org.eclipse.jdt.internal.core.index.impl.Index.merge(Index.java:249)
	at org.eclipse.jdt.internal.core.index.impl.Index.save(Index.java:354)
	at org.eclipse.jdt.internal.core.search.indexing.IndexManager.saveIndex
(IndexManager.java:423)
	at 
org.eclipse.jdt.internal.core.search.indexing.IndexManager.saveIndexes
(IndexManager.java:459)
	at org.eclipse.jdt.internal.core.search.indexing.IndexManager.notifyIdle
(IndexManager.java:297)
	at org.eclipse.jdt.internal.core.search.processing.JobManager.run
(JobManager.java:333)
	at java.lang.Thread.run(Thread.java:484)
Comment 1 Philipe Mulet CLA 2003-02-05 17:47:01 EST
This log occurs when crash recovery happened. 
Comment 2 Adam Kiezun CLA 2003-02-18 14:00:59 EST
got it again on 20030214
Comment 3 Kent Johnson CLA 2003-02-18 15:29:23 EST
So what were you doing at the time? Can you reproduce it?
Comment 4 Philipe Mulet CLA 2003-03-05 06:13:05 EST
Defer
Comment 5 Philipe Mulet CLA 2003-03-05 06:13:23 EST
Defer
Comment 6 Philipe Mulet CLA 2003-06-13 04:44:30 EDT
Reopening. Problem should go away with new implementation
Comment 7 Kent Johnson CLA 2004-02-17 14:22:03 EST
We have replaced the entire index infrastructure.

This bug is now obsolete.
Comment 8 Jerome Lanneluc CLA 2004-03-24 11:06:46 EST
Verified in build I200403240800.