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 210167 - Cpu profiling hangs profiled app.
Summary: Cpu profiling hangs profiled app.
Status: RESOLVED INCOMPLETE
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 7.1
Hardware: PC Linux
: P3 normal (vote)
Assignee: J Bachorik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-27 10:18 UTC by rad
Modified: 2012-04-11 12:38 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
profiled app thread dump (32.66 KB, text/plain)
2012-03-27 10:18 UTC, rad 		Details
thread dump of netbeans with runned profiler (35.38 KB, text/plain)
2012-03-28 11:06 UTC, rad 		Details
netbeans log (37.21 KB, text/x-log)
2012-03-28 11:06 UTC, rad 		Details
netbeans uigestures (3.89 KB, text/plain)
2012-03-28 11:07 UTC, rad 		Details
thread dump of profiled app (23.73 KB, text/plain)
2012-03-28 11:07 UTC, rad 		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 rad 2012-03-27 10:18:08 UTC 
Created attachment 117310 [details]
profiled app thread dump

Problematic area:

<0x76110000> (a [B):    0 Thread(s) sleeping, 8 Thread(s) waiting, 1 Thread(s) locking
    locked by "*** Profiler Agent Special Execution Thread 6" daemon prio=10 tid=0x7145b400 nid=0x165f in Object.wait() [0x713ae000]
        waits on monitor: "New I/O client worker #1-4" daemon prio=10 tid=0x704f3000 nid=0x1682 waiting for monitor entry [0x6f00e000]
        waits on monitor: "AWT-EventQueue-0" prio=10 tid=0x7085e000 nid=0x1673 waiting for monitor entry [0x70b0b000]
        waits on monitor: "RMI TCP Connection(2)-127.0.0.1" daemon prio=10 tid=0x6f454c00 nid=0x1699 waiting for monitor entry [0x6e5ae000]
        waits on monitor: "tasks:pool-1-thread-1" daemon prio=10 tid=0x70481400 nid=0x1675 waiting for monitor entry [0x705fe000]
        waits on monitor: "*** JFluid Monitor thread ***" daemon prio=10 tid=0x71459c00 nid=0x165e waiting for monitor entry [0x713ff000]
        waits on monitor: "Thread-7" daemon prio=10 tid=0x6f395400 nid=0x1683 waiting for monitor entry [0x6efbe000]
        waits on monitor: "tasks:pool-1-thread-3" daemon prio=10 tid=0x704b2400 nid=0x1679 waiting for monitor entry [0x70191000]
        waits on monitor: "tasks:pool-1-thread-2" daemon prio=10 tid=0x704b0800 nid=0x1678 waiting for monitor entry [0x701e1000]
Comment 1 J Bachorik 2012-03-28 09:19:50 UTC 
The profiler client awaits data from the profiled JVM. If you are able to reproduce the problem it would help greatly to include also the thread dump of the profiled JVM at the time of locking.
Comment 2 rad 2012-03-28 11:06:16 UTC 
Created attachment 117387 [details]
thread dump of netbeans with runned profiler
Comment 3 rad 2012-03-28 11:06:45 UTC 
Created attachment 117388 [details]
netbeans log
Comment 4 rad 2012-03-28 11:07:13 UTC 
Created attachment 117389 [details]
netbeans uigestures
Comment 5 rad 2012-03-28 11:07:43 UTC 
Created attachment 117390 [details]
thread dump of profiled app
Comment 6 rad 2012-03-28 11:12:27 UTC 
Problem on current my app always reproducible, but i has not rights to publication code of app.

I am attach thread dump from netbeans and profled app, and also part of netbeans log and uigestures
Comment 7 J Bachorik 2012-04-11 12:38:12 UTC 
The profiling IDE thread dump indicates there was a confirmation dialog visible at the time you took it. The dialog blocks the processing of the collected data and may pause the execution of the profiled application when the buffers overflow. Try to close the notification dialog and see whether this solves your problem.