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 64214 - Possible deadlock after an error in profiler
Summary: Possible deadlock after an error in profiler
Status: VERIFIED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@profiler
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2005-09-13 10:13 UTC by ehucka
Modified: 2007-09-28 09:14 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
error with threads dump (13.64 KB, text/plain)
2005-09-13 10:14 UTC, ehucka 		Details
another threadsdump (19.12 KB, text/plain)
2006-09-25 15:50 UTC, ehucka 		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 ehucka 2005-09-13 10:13:53 UTC 
After an error from sampled instrumentation the profiler blocked awt thread.
There is calling ProfilerClient.terminateTargetJVM, I think such methods should
not be called in AWT thread.
Comment 1 ehucka 2005-09-13 10:14:42 UTC 
Created attachment 24735 [details]
error with threads dump
Comment 2 iformanek 2005-09-19 13:14:15 UTC 
The deadlock is a post-symptom of critical error.
The error is entered as issue 64114 and already fixed, closing this as a 
duplicate.

*** This issue has been marked as a duplicate of 64114 ***
Comment 3 ehucka 2006-03-22 09:37:30 UTC 
verified
Comment 4 ehucka 2006-09-25 15:49:48 UTC 
I've seen something similar again in profiler dev 060925:

"AWT-EventQueue-1" prio=10 tid=0x0a16d800 nid=0x2fcc waiting for monitor entry
[0xb491a000..0xb491aec0]
   java.lang.Thread.State: BLOCKED (on object monitor)
com.sun.tools.profiler.ProfilerClient.terminateTargetJVM(ProfilerClient.java:757)
        - waiting to lock <0x7fdd3448> (a com.sun.tools.profiler.ProfilerClient)
com.sun.tools.profiler.TargetAppRunner.terminateTargetJVM(TargetAppRunner.java:494)
org.netbeans.modules.profiler.NetBeansProfiler.stopApp(NetBeansProfiler.java:907)
Comment 5 ehucka 2006-09-25 15:50:46 UTC 
Created attachment 34459 [details]
another threadsdump
Comment 6 ehucka 2006-09-25 15:54:22 UTC 
Steps to reproduce:

1. create an PaintApp nb sample project
2. start cpu profiling - entire application, profile only project classes

The application was blocked during starting. 
I cannot reproduce it again.
Comment 7 J Bachorik 2007-06-25 14:26:00 UTC 
this is probably fixed with the issue #82357
the fix addresses deadlocks caused by calling the "forceObtainedResults" method
Comment 8 ehucka 2007-07-10 09:52:36 UTC 
Could any profiler qe verify this? I do not profile regularly anything now so I cannot verify random issues. thanks
Comment 9 Alexander Kouznetsov 2007-09-28 09:14:53 UTC 
Verified