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.
Build: NetBeans IDE Dev (Build 20111006-c210522a9c40) VM: OpenJDK 64-Bit Server VM, 20.0-b11, OpenJDK Runtime Environment, 1.6.0_22-b22 OS: Linux Stacktrace: java.lang.NullPointerException at org.netbeans.modules.profiler.drilldown.DrilldownContributor.showDrillDown(DrilldownContributor.java:177) at org.netbeans.modules.profiler.drilldown.DrilldownContributor.addToCpuResults(DrilldownContributor.java:94) at org.netbeans.modules.profiler.LiveResultsWindow.preparePanelForInstrType(LiveResultsWindow.java:1012) at org.netbeans.modules.profiler.LiveResultsWindow.updateResultsDisplay(LiveResultsWindow.java:1132) at org.netbeans.modules.profiler.LiveResultsWindow.access$100(LiveResultsWindow.java:131) at org.netbeans.modules.profiler.LiveResultsWindow$ResultsMonitor$1.run(LiveResultsWindow.java:212)
Created attachment 111580 [details] stacktrace
Created attachment 111581 [details] stacktrace
Steps: - clean userdir or NO profiler window open (like Control Panel, Telemetry etc.) - start cpu profiling, default settings - once the profiling session is FULLY started, open the live results Doesn't seem to be reproducible with the Control Panel window persisted & opened from the previous IDE session.
Caused by TargetAppRunner.getDefault() == null at DrilldownContributor.java:177. Might be related to http://hg.netbeans.org/profiler-main/rev/29cb4f37f1aa. Jardo please check whether null default TargetAppRunner is the correct behavior.
FIxed in profiler-main changeset: 203557:ffbd60d200d3 user: Tomas Hurka <thurka@netbeans.org> date: Thu Oct 06 16:46:56 2011 +0200 summary: bugfix #203196, partial rollback of 29cb4f37f1aa since ServiceLoader.load() does not work well in NetBeans modules context
Integrated into 'main-golden' Changeset: http://hg.netbeans.org/main-golden/rev/ffbd60d200d3 User: Tomas Hurka <thurka@netbeans.org> Log: bugfix #203196, partial rollback of 29cb4f37f1aa since ServiceLoader.load() does not work well in NetBeans modules context