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: | [windows]Deadlock after dettach frame | ||
---|---|---|---|
Product: | platform | Reporter: | Jan Lahoda <jlahoda> |
Component: | -- Other -- | Assignee: | David Simonek <dsimonek> |
Status: | CLOSED FIXED | ||
Severity: | blocker | ||
Priority: | P1 | ||
Version: | 3.x | ||
Hardware: | Sun | ||
OS: | Solaris | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | Full thread dump of the deadlock. |
Description
Jan Lahoda
2001-03-30 08:30:41 UTC
Created attachment 922 [details]
Full thread dump of the deadlock.
I tried to reproduce this, but was not successfull. Yes! Finally!!! Thanks, Jan. From the stack trace, I found out that actions like DetachFrame, AttachFrame and so are badly written, because they run on live Swing's structures, but in non-AWT thread. Surely this is the root of your problems (and problems of probably several others). THANKS! If this targets more than one action, the deadlock/fall_down/anything can occur nearly anytime one tries to do something with windows. I think this is really dangerous. Well, it is dangerous, but the deadlock doesn't occur so often. Don't worry, I'm working on it. (or did you just want to raise the number of P1 bugs that we have? :-)) Fixed both in main trunk and 3.2. Window system related actions replanned correctly to AWT thread. Target milestone 3.2 I played with this for a while and it looks OK. Development build 209 and releasse 3.2, build 38. Resolved for 3.4.x or earlier, no new info since then -> closing. |