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 234135 - for CPU monitoring, add a mode that only records stack traces for threads that are blocked on a monitor
Summary: for CPU monitoring, add a mode that only records stack traces for threads tha...
Status: NEW
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 7.4
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-08 12:32 UTC by grandinj
Modified: 2013-08-08 12:32 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
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 grandinj 2013-08-08 12:32:28 UTC 
Use case:
I am experiencing jitter/stuttering in my user interface i.e. it sometimes takes a little while to respond.
From the profiler I can see that CPU usage on my event thread is pretty low, but that it periodically gets in the MONITOR state for periods ranging from 100 to 500ms.
I'm pretty sure that it's because some event thread code is trying to acquire a lock that being held for long periods of time by some other code on another thread.
But this is a large and thread-heavy application, so it's tricky to figure out.

Proposed solution:
Under the CPU monitoring tab, have a new option "Profile Locks".
When enabled, the Profiler should only store a call trace for a thread when that particular thread is blocked on a monitor.
Given enough time to run under the profiler, this will effectively turn the usual CPU usage call hierachy views into pretty awesome locking usage views.