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 220734 - deadlock with sampler
Summary: deadlock with sampler
Status: RESOLVED DUPLICATE of bug 213926
Alias: None
Product: ide
Classification: Unclassified
Component: Slowness Detector (show other bugs)
Version: 7.3
Hardware: PC Mac OS X
: P1 normal (vote)
Assignee: Tomas Hurka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-24 11:15 UTC by Milos Kleint
Modified: 2012-10-24 16:10 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
thread dump (34.34 KB, text/plain)
2012-10-24 11:15 UTC, Milos Kleint 		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 Milos Kleint 2012-10-24 11:15:58 UTC 
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.
Comment 1 Jaroslav Tulach 2012-10-24 15:56:24 UTC 
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?
Comment 2 Tomas Hurka 2012-10-24 16:01:06 UTC 
Yes, this is a known bug in JDK. It is fixed in JDK 7 update 10.
Comment 3 Tomas Hurka 2012-10-24 16:10:50 UTC 

*** This bug has been marked as a duplicate of bug 213926 ***