Bug 55279 - NPE in IndexManager.rebuildIndex
Summary: NPE in IndexManager.rebuildIndex
Status: RESOLVED DUPLICATE of bug 52619
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   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: 2004-03-18 15:40 EST by Nick Edgar CLA
Modified: 2004-03-19 13:11 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 Nick Edgar CLA 2004-03-18 15:40:25 EST
build I20040318

Got an unrelated error on startup (Sync view problems), which caused the
Workbench to shut down (another problem).  Noticed the following in the console.
No corresponding entry in the log.

java.lang.NullPointerException
        at
org.eclipse.jdt.internal.core.search.indexing.IndexManager.rebuildIndex(IndexManager.java:325)
        at
org.eclipse.jdt.internal.core.search.indexing.IndexManager.getIndex(IndexManager.java:125)
        at
org.eclipse.jdt.internal.core.search.PatternSearchJob.getIndexes(PatternSearchJob.java:103)
        at
org.eclipse.jdt.internal.core.search.PatternSearchJob.execute(PatternSearchJob.java:65)
        at
org.eclipse.jdt.internal.core.search.processing.JobManager.performConcurrentJob(JobManager.java:261)
        at
org.eclipse.jdt.core.search.SearchEngine.searchAllTypeNames(SearchEngine.java:825)
        at
org.eclipse.jdt.internal.corext.util.AllTypesCache.search(AllTypesCache.java:440)
        at
org.eclipse.jdt.internal.corext.util.AllTypesCache$TypeCacher.doSearchTypes(AllTypesCache.java:129)
        at
org.eclipse.jdt.internal.corext.util.AllTypesCache$TypeCacher.run(AllTypesCache.java:98)
Comment 1 Olivier Thomann CLA 2004-03-18 16:05:12 EST
Line 325 is:
		request = new AddJarFileToIndex((IFile) target, this);

I don't see how you can get a NPE on that line. What VM are you using?
Comment 2 Nick Edgar CLA 2004-03-18 16:38:11 EST
You can probably ignore this.  I just realized I was accidentally running
I20040219.  When I switched back to I20040318, I didn't see any problems.
But if you wanted to, you could see what line 325 was in I20040219.

Comment 3 Nick Edgar CLA 2004-03-18 16:39:14 EST
To clarify, I was running I20040219 on a workspace most recently saved with
I20040318, so the index structure may have changed.
Comment 4 Kent Johnson CLA 2004-03-19 13:11:22 EST
We had thread issues with shutdown.

*** This bug has been marked as a duplicate of 52619 ***