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 207061 - New Runnables always instrumented for no profiling roots
Summary: New Runnables always instrumented for no profiling roots
Status: NEW
Alias: None
Product: profiler
Classification: Unclassified
Component: Engine (show other bugs)
Version: 5.x
Hardware: All All
: P4 normal (vote)
Assignee: Tomas Hurka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-09 13:06 UTC by Jiri Sedlacek
Modified: 2012-01-09 13:06 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Sedlacek 2012-01-09 13:06:07 UTC
Dynamic attach to external application, profile application, all defaults (== no profiling roots, do not profile new Threads/Runnables).

When attached to a Swing application and doing some load (clicking buttons etc.) the profiler instruments some runnables:

 - javax.swing.RepaintManager$ProcessingRunnable.run()
 - sun.awt.GlobalCursorManager$NativeUpdater.run()

It looks like the advanced option "Profile new Threads/Runnables" is not strictly followed by the profiling engine. Either it should be followed or the UI option should be selected & disabled if new Runnables will always be instrumented.