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.

Bug 39683 - [JDK1.5.0] IDE frozen when opening form
Summary: [JDK1.5.0] IDE frozen when opening form
Status: VERIFIED WORKSFORME
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: mslama
URL:
Keywords: JDK_SPECIFIC
Depends on:
Blocks:
 
Reported: 2004-02-06 08:52 UTC by Milan Kubec
Modified: 2008-12-23 09:44 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
thread dumps (52.78 KB, text/plain)
2004-02-06 11:10 UTC, Milan Kubec
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Milan Kubec 2004-02-06 08:52:04 UTC
[release351, JDK 1.5.0 Beta 1]
IDE got frozen when opening form file. Attachment
contains 3 thread dumps within one minute. Doesn't
seem to be reproducible on trunk builds. It seems
to be fixed by new winsys.
Comment 1 Milan Kubec 2004-02-06 09:03:37 UTC
Happens only in MDI.
Comment 2 Marian Mirilovic 2004-02-06 10:39:59 UTC
Milan, 
two reasons why I close this one as WORKSFORME (I hope you agree:) :
1 - no attachment
2 - if you cannot reproduce on trunk, it's already fixed or ..., but
it works
Comment 3 Milan Kubec 2004-02-06 11:10:58 UTC
Created attachment 13290 [details]
thread dumps
Comment 4 Milan Kubec 2004-02-06 11:15:11 UTC
I've attached thread dumps and reopened the issue, since I think that
reproducing deadlock is not that easy sometimes and I would like those
thread dumps be evaluated by developer.
Comment 5 Marian Mirilovic 2004-02-06 13:02:10 UTC
> I would like those thread dumps be evaluated by developer.
Why you don't believe me ? :(

Ok, reassigne to Marek for ? evaluation ?

Marek:
- issue is reproducible only in 3.5 - not 3.6 (I think strong argument
for closing as WORKSFORME)
- org.netbeans.core.windows.frames.SplitContainerImpl is no more in
the production code (I think second strong argument for closing as
WORKFORME)


Comment 6 Milan Kubec 2004-02-06 13:16:39 UTC
You are almost developer :-) and I believe you, but even you didn't
have chance to evaluate those dumps before closing it if they were not
attached previously. But if you evaluate and write "Code in thread
dumps is not more in service" or "it's fixed" and close the issue,
I'll be perfectly OK with it.
Comment 7 Marian Mirilovic 2004-02-06 13:57:27 UTC
;) Dik