This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
| Summary: | Deadlock in InheritanceSupport | ||
|---|---|---|---|
| Product: | java | Reporter: | Petr Nejedly <pnejedly> |
| Component: | Unsupported | Assignee: | issues@java <issues> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | blocker | Keywords: | RANDOM, THREAD |
| Priority: | P2 | ||
| Version: | 3.x | ||
| Hardware: | Sun | ||
| OS: | Solaris | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Attachments: | The deadlock stack traces | ||
|
Description
Petr Nejedly
2003-08-05 09:55:31 UTC
Created attachment 11212 [details]
The deadlock stack traces
Actually, it happened to me in 3.5.1, but we have no such version entry... Please, provide steps how to reproduce it. Thanks. I hope it doesn't matter, you see two threads running in paralel and acquiring locks in different order, which is always wrong and always potential deadlock. IIRC, I've only invoked popup->new->JFrame when I was already on (so far empty) gui editing workspace. I cannot recall whether I've already filled in the form name and pressed finish.. It does matter. Steps can be used to verify the fix and also to set the priority of the issue. In this case I am lowering priority to P2. *** Issue 35544 has been marked as a duplicate of this issue. *** The affected code has been refactored and simplified. Namely InheritanceSupport (now InheritanceSupport2) and JavaWizard. Closed as WONTFIX. Reorganization of java component |