Summary: | [search] NPE in JavaSearchScope | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Chris Aniszczyk <caniszczyk> |
Component: | Core | Assignee: | Frederic Fusier <frederic_fusier> |
Status: | VERIFIED DUPLICATE | QA Contact: | |
Severity: | normal | ||
Priority: | P2 | CC: | daniel_megert, jerome_lanneluc |
Version: | 3.4 | ||
Target Milestone: | 3.4 M7 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Chris Aniszczyk
2008-01-29 12:15:23 EST
Most likely caused by fix for bug 215841. (In reply to comment #1) > Most likely caused by fix for bug 215841. > How could it be as this bug was released yesterday and the corresponding I-build is not on the download page yet!?? The build ref is I20071213-1700 (aka 3.4M4) Can you also explain why did you increase the severity? >How could it be as this bug was released yesterday and the corresponding >I-build is not on the download page yet!?? The build ref is I20071213-1700 (aka >3.4M4) > >Can you also explain why did you increase the severity? Sorry, I didn't look at the build id, just remembered recent incoming code change in that class. (In reply to comment #3) > Sorry, I didn't look at the build id, just remembered recent incoming code > change in that class. > No problem :-) It seems to be a potential problem from the beginning with the initialization of the JavaWorkspaceScope global variable stored in the JavaModelManager. I cannot see any synchronization which would make it thread safe and I guess that 2 threads trying to get a java workspace scope concurrently on the first place may fall into such problematic situation... *** This bug has been marked as a duplicate of bug 158526 *** Verified for 3.4 M7 by code inspection of v_856. |