Summary: | hang loading plugin (during validation) | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Barry Searle <searle> | ||||
Component: | Resources | Assignee: | Platform-Resources-Inbox <platform-resources-inbox> | ||||
Status: | CLOSED INVALID | QA Contact: | |||||
Severity: | critical | ||||||
Priority: | P2 | CC: | paulacox | ||||
Version: | 1.0 | ||||||
Target Milestone: | --- | ||||||
Hardware: | PC | ||||||
OS: | Windows NT | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Barry Searle
2002-05-16 09:42:52 EDT
Created attachment 863 [details]
javacore dump from hang
What a mess! There seem to be four "active" threads, two are classloading, and two are doing other things. It is not clear that this is "our fault". Classloading always happens in a critical region, so it will always have some lock acquired during this process. I don't know what has caused the other two threads to be blocked. Why are there so many threads trying to work at once? The deadlock could be caused by that DTD tooling code, since three of the threads are running code in "com.ibm.etools.dtd.". I suggest that someone who is familiar with that (WSAD?) code should take a look at those stack traces and figure out what is happening. This is being investigated by WSAD. Please re-open if you determine this is a Platform problem. old bug. closing. |