Bug 17562 - Race condition on startup leads to 2 JavaModel instances
Summary: Race condition on startup leads to 2 JavaModel instances
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 critical (vote)
Target Milestone: 2.0 F2   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-24 03:31 EDT by Dani Megert CLA
Modified: 2002-06-03 08:44 EDT (History)
0 users

See Also:

Attachments
stack trace (4.54 KB, text/plain)
2002-05-24 03:31 EDT, Dani Megert CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dani Megert CLA 2002-05-24 03:31:11 EDT 
Build F1
Indexer and main thread can get different Java Model instances
See attached stack traces.

This can lead to a various number of bugs in the UI e.g. Java working sets don't
work because the elements are no longer equal (different Java Model instances as
parent).
Comment 1 Dani Megert CLA 2002-05-24 03:31:36 EDT 
Created attachment 1025 [details]
stack trace
Comment 2 Philipe Mulet CLA 2002-05-24 07:27:20 EDT 
JavaModel handles are indeed supposed to be unique (for comparison purpose).
Fixed by ensuring only one handle can ever be allocated.
Comment 3 Philipe Mulet CLA 2002-05-24 13:12:45 EDT 
Fixed
Comment 4 Jerome Lanneluc CLA 2002-06-03 08:44:20 EDT 
Verified