Summary: | Possible deadlock initializing jdt.core | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Olivier Thomann <Olivier_Thomann> |
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | pascal |
Version: | 3.1 | ||
Target Milestone: | 3.1 M4 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Olivier Thomann
2004-12-15 15:38:46 EST
Can someone explain how this show a deadlock ? Where is the second thread ? This stack trace is pretty useless as it is. The problem here is not a deadlock but actually a concurrency problem while JDT core is starting. The message indicates that while "Worker-2" thread was activating the jdt core plugin, the thread "worker-4" has been trying to load a class (from jdt core) and that the loading of this class has been delayed until the startup of jdt core startup is over (or a 5s delay has expired). Thanks Pascal, but I don't see how we can identify the problem without knowing which classes were being loaded concurrently, what was the stacks of the threads at the time the timeout occured, etc. I entered bug 81423 and will close this one for lack of information. |