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.
Profiler 070314 NetBeans IDE Dev (Build 200703141900) 1.6.0; Java HotSpot(TM) Client VM 1.6.0-b105 Windows XP version 5.1 running on x86 ru_RU (nb); Cp1251 Steps to reproduce: - Insert Reset Results and Take Snapshot Profiling Points on the same line of Anagram Game application (first line of nextTrial...() method body) - Start Analyze Performance Task with Entire Application and Profile Only Project Files options set - Press Next Word button in Anagram Game application - RESULT: NPE is thrown and PPs stop to work. Trying to perform some other actions will cause IDE to hang. And it can't even be exited correctly. java.lang.NullPointerException at com.sun.tools.profiler.results.cpu.CPUResultsSnapshot.<init>(CPUResultsSnapshot.java:93) ... or java.lang.NullPointerException at com.sun.tools.profiler.results.cpu.CPUCallGraphBuilder.methodEntry(CPUCallGraphBuilder.java:71)
Created attachment 39543 [details] Exception
Created attachment 39544 [details] Another exception
Created attachment 39545 [details] Messages.log
Please use text/plain MIME type when attaching exceptions.
assigning
fixed in trunk
Failed to verify with Profiler 070323 Always get the following exception: com.sun.tools.profiler.results.cpu.CPUResultsSnapshot$NoDataAvailableException at com.sun.tools.profiler.results.cpu.CPUResultsSnapshot.<init>(CPUResultsSnapshot.java:95) Lowering the priority since IDE doesn't tend to hovering.
Created attachment 39981 [details] Exception
The observed behavior is caused by the fact that you place both PPs on the beginning of the line. Thus virtually cleaning all results and immediately after that taking snapshot of no results. You should place "ResetResults" on the line beginning and "TakeSnapshot" on the line end. That way you will get a snapshot of results generated by the selected line. I still do insist that the issue filed here originally has been fixed. I'm creating a new issue #99078 for the problem you've described
Verified