Bug 226849 - [model] NPE in ExternalPackageFragmentRoot.hashCode
Summary: [model] NPE in ExternalPackageFragmentRoot.hashCode
Status: VERIFIED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.4   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: 3.5 M1   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-13 19:07 EDT by Michael Fraenkel CLA
Modified: 2013-08-09 06:08 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Fraenkel CLA 2008-04-13 19:07:04 EDT
Build ID: 3.4M6

Steps To Reproduce:
Not sure.

java.lang.NullPointerException
	at org.eclipse.jdt.internal.core.ExternalPackageFragmentRoot.hashCode(ExternalPackageFragmentRoot.java:96)
	at org.eclipse.jdt.internal.core.PackageFragment.hashCode(PackageFragment.java:360)
	at org.eclipse.jdt.internal.core.ClassFile.hashCode(ClassFile.java:573)
	at org.eclipse.jdt.internal.core.JavaElement.hashCode(JavaElement.java:467)
	at org.eclipse.jdt.internal.core.search.JavaSearchTypeNameMatch.hashCode(JavaSearchTypeNameMatch.java:72)
	at java.util.HashMap.put(HashMap.java:418)
	at org.eclipse.jdt.internal.corext.util.OpenTypeHistory.createFromElement(OpenTypeHistory.java:410)
	at org.eclipse.jdt.internal.corext.util.History.load(History.java:272)
	at org.eclipse.jdt.internal.corext.util.History.load(History.java:164)
	at org.eclipse.jdt.internal.corext.util.OpenTypeHistory.<init>(OpenTypeHistory.java:199)
	at org.eclipse.jdt.internal.corext.util.OpenTypeHistory.getInstance(OpenTypeHistory.java:185)
	at org.eclipse.jdt.internal.ui.JavaPlugin.initializeAfterLoad(JavaPlugin.java:383)
	at org.eclipse.jdt.internal.ui.InitializeAfterLoadJob$RealJob.run(InitializeAfterLoadJob.java:36)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

More information:
Comment 1 Jerome Lanneluc CLA 2008-04-24 09:53:33 EDT
Looking at the code, I don't see how this can happen. Do you have more details?
Comment 2 Michael Fraenkel CLA 2008-04-24 10:08:11 EDT
Nope...
I know once I hit this, I have to start a new workspace.

I will see if I can come up with a scenario to reproduce.
Comment 3 Jerome Lanneluc CLA 2008-06-26 09:54:43 EDT
Please reopen if you have more details.
Comment 4 Kent Johnson CLA 2008-08-06 14:41:18 EDT
Verified for 3.5M1 using I20080805-1307
Comment 5 Tobias Bertelsen CLA 2013-08-09 06:08:13 EDT
This still happens in rare cases. Another bug has been opened: https://bugs.eclipse.org/bugs/show_bug.cgi?id=396854