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 230280 - deadlock.detector.Detector$DeadlockDetectedException with only one thread!
Summary: deadlock.detector.Detector$DeadlockDetectedException with only one thread!
Status: RESOLVED INCOMPLETE
Alias: None
Product: ide
Classification: Unclassified
Component: Slowness Detector (show other bugs)
Version: 7.4
Hardware: All All
: P3 normal (vote)
Assignee: David Strupl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-26 11:13 UTC by szmitek
Modified: 2013-06-04 12:15 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 200921

Attachments
stacktrace (4.91 KB, text/plain)
2013-05-26 11:13 UTC, szmitek 		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 szmitek 2013-05-26 11:13:26 UTC 
Build: NetBeans IDE Dev (Build 201305252300)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.0-b33, Java(TM) SE Runtime Environment, 1.8.0-ea-b91
OS: Linux

User Comments:
szmitek: Activating plugin took very long time and I cannot stop it.




Stacktrace: 
org.netbeans.modules.deadlock.detector.Detector$DeadlockDetectedException
   at java.lang.Throwable.getStackTraceElement(Throwable.java:0)
   at java.lang.Throwable.getOurStackTrace(Throwable.java:827)
   at java.lang.Throwable.getStackTrace(Throwable.java:816)
   at org.openide.util.RequestProcessor$SlowItem.fillInStackTrace(RequestProcessor.java:1849)
   at java.lang.Throwable.<init>(Throwable.java:250)
   at java.lang.Exception.<init>(Exception.java:54)
Comment 1 szmitek 2013-05-26 11:13:28 UTC 
Created attachment 134909 [details]
stacktrace
Comment 2 Jaroslav Tulach 2013-06-04 06:20:39 UTC 
Davide, these messages are coming from your invention, right? Can you please help me understand what is going on. How can a deadlock be caused by a single thread? I was assuming you need two.
Comment 3 David Strupl 2013-06-04 11:20:21 UTC 
Please have a look at your messages.log. Several consecutive exceptions are the threads deadlocked (with the same file name). You should be able to see the full thread dump in that file.

But please note that deadlock detection in JDK 8 is most probably broken (as it reports bogus deadlocks).
Comment 4 Tomas Hurka 2013-06-04 12:15:07 UTC 
The full info is available in /tmp/deadlock4228139141833554036.txt file. It would be great if you can attach it to this bug. Thanks.