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 with sampler | ||
|---|---|---|---|
| Product: | ide | Reporter: | Milos Kleint <mkleint> |
| Component: | Slowness Detector | Assignee: | Tomas Hurka <thurka> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | jtulach |
| Priority: | P1 | ||
| Version: | 7.3 | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Issue Type: | DEFECT | Exception Reporter: | |
| Attachments: | thread dump | ||
I happily let Tomáš as the author of the sampler and the one of us who has a Mac deal with the deadlock. Found one Java-level deadlock: ============================= "Timeable Event Queue Watch Dog": waiting for ownable synchronizer 0x000000012bc1c850, (a java.util.concurrent.locks.ReentrantLock$NonfairSync), which is held by "AWT-EventQueue-1" "AWT-EventQueue-1": waiting to lock monitor 0x00007fc2d265b840 (object 0x000000012bc1cc00, a sun.awt.PostEventQueue), which is held by "TimerQueue" "TimerQueue": waiting for ownable synchronizer 0x000000012bc1c850, (a java.util.concurrent.locks.ReentrantLock$NonfairSync), which is held by "AWT-EventQueue-1" I have to admit I still don't see the deadlock. I am not trained in reading the concurrent.locks yet. Anyway I believe this is a JDK bug: Why should a simple call to isEventDispatchThread() cause a deadlock? Yes, this is a known bug in JDK. It is fixed in JDK 7 update 10. *** This bug has been marked as a duplicate of bug 213926 *** |
Created attachment 126452 [details] thread dump java version "1.7.0_07" Java(TM) SE Runtime Environment (build 1.7.0_07-b10) Java HotSpot(TM) 64-Bit Server VM (build 23.3-b01, mixed mode) that's the version I installed today, then through the Java preferences panel, updated to Update 9 (only visible in the UI, not through java --version recently updated to latest jdk from oracle, because apple discontinued the 1.6 version more or less.