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.
Steps (the same as for Bug 240063, might be related) 1/ Win7 64b, 7u45 64b, Anagram Game 2/ Custom CPU, advanced, all advanced settings selected 3/ Start profiling, NPE shows immediately after displaying Locks window In the corresponding bugdb, these exceptions are thrown: java.lang.NullPointerException at org.netbeans.lib.profiler.results.cpu.CPUCallGraphBuilder.markerMethodEntry (CPUCallGraphBuilder.java:1143) java.lang.NullPointerException at org.netbeans.lib.profiler.results.cpu.CPUCallGraphBuilder.plainMethodEntry (CPUCallGraphBuilder.java:1222) See the bugdb for more details.
Another bugdb report, happens also for Methods/Sampling.
The case with CPU instrumentation is fixed in profiler-main changeset: 284910:5de10ecc73a9 user: Tomas Hurka <thurka@netbeans.org> date: Wed Mar 18 18:13:57 2015 +0100 summary: bugfix #240084, initialize hasMonitorInfo using isLockContentionMonitoringEnabled() - NEW_MONITOR event can arrive after METHOD_ENTRY_MONITOR (due to thread-local data buffers) and in such case hasMonitorInfo is set incorrectly when METHOD_ENTRY_MONITOR is processed Sampling case is different issue.
Integrated into 'main-silver', will be available in build *201503200001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/5de10ecc73a9 User: Tomas Hurka <thurka@netbeans.org> Log: bugfix #240084, initialize hasMonitorInfo using isLockContentionMonitoringEnabled() - NEW_MONITOR event can arrive after METHOD_ENTRY_MONITOR (due to thread-local data buffers) and in such case hasMonitorInfo is set incorrectly when METHOD_ENTRY_MONITOR is processed