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.
| Summary: | Deadlock in performance tests (jemmy vs core) | ||
|---|---|---|---|
| Product: | qa | Reporter: | Alexander Pepin <apepin> |
| Component: | Jellytools | Assignee: | issues@qa <issues> |
| Status: | NEW --- | ||
| Severity: | normal | CC: | issues |
| Priority: | P2 | ||
| Version: | 7.0.1 | ||
| Hardware: | PC | ||
| OS: | All | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Attachments: | stack dump | ||
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" |
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.