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 199188 - Deadlock in performance tests (jemmy vs core)
Summary: Deadlock in performance tests (jemmy vs core)
Status: NEW
Alias: None
Product: qa
Classification: Unclassified
Component: Jellytools (show other bugs)
Version: 7.0.1
Hardware: PC All
: P2 normal (vote)
Assignee: issues@qa
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-06 09:54 UTC by Alexander Pepin
Modified: 2011-06-06 22:06 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
stack dump (35.86 KB, text/plain)
2011-06-06 09:54 UTC, Alexander Pepin 		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 Alexander Pepin 2011-06-06 09:54:53 UTC 
Created attachment 108747 [details]
stack dump

Since recent time we face with deadlocks while running performance tests. These deadlocs break the performance tests. Please investigate.
Comment 1 Vladimir Voskresensky 2011-06-06 16:53:23 UTC 
This is a deadlock between org.netbeans.jemmy.QueueTool$JemmyQueue and org.netbeans.core.TimableEventQueue:
Found one Java-level deadlock:
=============================
"AWT-EventQueue-2":
  waiting to lock monitor 0x0a07f758 (object 0xebf5a580, a org.netbeans.jemmy.QueueTool$JemmyQueue),
  which is held by "main"
"main":
  waiting to lock monitor 0x08c04ba4 (object 0xeaf3d020, a java.awt.EventQueue),
  which is held by "AWT-XAWT"
"AWT-XAWT":
  waiting to lock monitor 0x0866bb00 (object 0xeb832df0, a org.netbeans.core.TimableEventQueue),
  which is held by "main"