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 37457 - deadlock in unit tests
Summary: deadlock in unit tests
Status: VERIFIED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: Window System (show other bugs)
Version: 3.x
Hardware: PC Linux
: P1 blocker (vote)
Assignee: Peter Zavadsky
URL:
Keywords: THREAD
Depends on:
Blocks:
 
Reported: 2003-11-24 16:12 UTC by pzajac
Modified: 2008-12-22 22:51 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
threads dump (28.36 KB, text/plain)
2003-11-24 16:15 UTC, pzajac 		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 pzajac 2003-11-24 16:12:59 UTC 
[200311241900]
Deadlock occured when the openide/unit tests were
runned.
Comment 1 pzajac 2003-11-24 16:15:54 UTC 
Created attachment 12276 [details]
threads dump
Comment 2 _ ttran 2003-11-24 16:25:20 UTC 
pzajac: next time please mark deadlock issues w/ THREAD keyword.  Thx
Comment 3 Peter Zavadsky 2003-11-24 16:38:13 UTC 
Now I wonder window system should schedule the component(De)Activated
into AWT thread if needed, that's possible hot fix. Thinking whether I
apply it now.

On the other hand winsys should be single threaded (see threading),
thus calling TC.requestActive outside AWT thread is from this point of
view incorrect.

It seems there is a time to introduce the assert isEventDispatchThread
at the begining of API methods.
Comment 4 Peter Zavadsky 2003-11-24 17:13:26 UTC 
Fixed in [trunk]

The hot fix:

core/windows/../WindowManagerImpl.java 1.8
Comment 5 pzajac 2003-11-26 13:09:47 UTC 
No deadlock occured in unit tests.