Summary: | NPE searching for references to a message | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Peter Burka <peter_burka> |
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | ||
Version: | 2.0 | ||
Target Milestone: | 2.0 F3 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Peter Burka
2002-06-03 16:59:29 EDT
I had recently deleted a file from the same package as this message. I just noticed that the deleted file was still open in an editor, somehow. I've also zipped up the contents of my D:\eclipse\workspace\.metadata\.plugins\org.eclipse.jdt.core directory. For some reason I can't add them as an attachment (it's 5MB). Please e-mail me if you want these. Or you can just FTP it from ott2f/.../accounts/peterb/public/index-for-18920.zip Closing the open editor seems to have made the bug go away. Steps to repeat: - open a Java file and modify it - switch editors so that the dirty file isn't the active editor - from a second window, in the Resource perspective, delete the dirty file - perform a search Thanks for the test case Peter. Note that leaving the dirty editor open is a feature from JDT/UI (so that you don't loose your changes). When collecting the paths of the working copies, the match locator was incorrectly using getUnderlyingResource().getFullPath() that would throw an exception and leave the file path list with <null> if the file did not exist. Fixed by using the handle only method getPath() on the java element instead. Verified. I got a OutOfMemoryError, but this is related to the VM args I used to start the self hosting workspace. Verified. |