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 37793 - Deadlock in StatusBar
Summary: Deadlock in StatusBar
Status: VERIFIED WONTFIX
Alias: None
Product: editor
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: PC Linux
: P2 blocker (vote)
Assignee: Miloslav Metelka
URL:
Keywords: RANDOM, THREAD
Depends on:
Blocks:
 
Reported: 2003-12-05 14:07 UTC by ehucka
Modified: 2007-11-05 13:44 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Thread dump. (8.04 KB, text/plain)
2003-12-05 14:09 UTC, ehucka 		Details
Threaddump, JDK 1.4.2_03, build 200401061900 (11.30 KB, text/plain)
2004-01-07 12:38 UTC, ehucka 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ehucka 2003-12-05 14:07:39 UTC 
Build 200312041900

I've seen it twice in this build.
Comment 1 ehucka 2003-12-05 14:09:47 UTC 
Created attachment 12437 [details]
Thread dump.
Comment 2 ehucka 2004-01-07 12:36:56 UTC 
I have another threaddump from deadlock. Maybe it is the same problem.
I got it when I tried to open many java files at once.
Comment 3 ehucka 2004-01-07 12:38:12 UTC 
Created attachment 12744 [details]
Threaddump, JDK 1.4.2_03, build 200401061900
Comment 4 Miloslav Metelka 2004-01-07 20:38:58 UTC 
It seems like a JDK problem - counterlocking TimerQueue against AWT
thread. We should search the bug parade whether this is a known issue
or not. Maybe we should also try older JDKs like 1.4.2_02 whether this
is a new problem local just to 1.4.2_03.
Comment 5 Miloslav Metelka 2004-01-19 16:12:43 UTC 
Petre, could you please try to reproduce it (maybe together with Eman)
and if you succeed on 1.4.2_03, could you please try it on 1.4.2_02? I
would like to know whether this is a problem of a single JDK version
only or whether something was changed in the IDE which might evoke
this problem. Thanks.
Comment 6 pfelenda 2004-01-20 14:19:01 UTC 
I am not able to reproduce it. I tried run in on both jdks.
Comment 7 Miloslav Metelka 2004-01-22 18:54:19 UTC 
I looked again at both attached thread dumps:
ad 1.dump) I do not clearly understand why the TimerQueue is waiting
for AppContext's monitor - there seems to be no other thread has
acquired that lock.
ad 2.dump) the same with TimerQueue acquiring EventQueue lock - there
seems to be no other thread holding the monitor.

This has to be resolved into 3.6.
Comment 8 Miloslav Metelka 2004-01-27 12:48:12 UTC 
I've found an issue that looks similar to this - it's
http://developer.java.sun.com/developer/bugParade/bugs/4852507.html
The TimerQueue thread is also waiting on AppContext monitor with no
apparent reason.

I was told by Petr Nejedly (added to cc) that he has also seen these
kinds of spurious deadlocks (with TimerQueue waiting on monitor)
appear on Linux.

I have added a note to 4852507. I'm closing this issue as wontfix.
Comment 9 ehucka 2006-03-22 09:31:47 UTC 
verified