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 98389 - A deadlock after stop test started internally
Summary: A deadlock after stop test started internally
Status: CLOSED WONTFIX
Alias: None
Product: qa
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@qa
URL:
Keywords: RANDOM, THREAD
Depends on:
Blocks:
 
Reported: 2007-03-20 18:51 UTC by ehucka
Modified: 2011-02-17 09:31 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
threaddump (29.44 KB, text/plain)
2007-03-20 18:53 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 2007-03-20 18:51:59 UTC 
NetBeans IDE Dev (Build 200703191900)
1.6.0; Java HotSpot(TM) Client VM 1.6.0-b105
Linux version 2.6.16-1.2122_FC5 running on i386
en_US (nb); UTF-8

A random deadlock occurred after I stopped task of internal test execution in
output window. I started a debugger ui test.

I do not know if it is the right component.
Comment 1 ehucka 2007-03-20 18:53:17 UTC 
Created attachment 39716 [details]
threaddump
Comment 2 Marian Mirilovic 2011-02-17 08:54:22 UTC 
Jemmy sources/the whole project was moved to java.nt. In case  you still want to get issue fixed, please report it here :
http://java.net/jira/browse/JEMMY