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.
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.