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 249323 - NPE in CPUCallGraphBuilder.plainMethodEntry (modify profiling)
Summary: NPE in CPUCallGraphBuilder.plainMethodEntry (modify profiling)
Status: RESOLVED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Engine (show other bugs)
Version: 8.1
Hardware: All All
: P3 normal (vote)
Assignee: Tomas Hurka
URL:
Keywords:
: 249324 249457 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-12-12 13:56 UTC by Jiri Sedlacek
Modified: 2015-04-21 17:31 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
IDE logfile (301.60 KB, application/octet-stream)
2014-12-12 13:56 UTC, Jiri Sedlacek 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Sedlacek 2014-12-12 13:56:49 UTC 
Created attachment 151075 [details]
IDE logfile

Steps:

 0/ 1.7.0_72 64-bit, Java2Demo
 1/ Methods profiling, Selected methods defined 10 methods, do not start!
 2/ Switch to Objects profiling, Selected classes, defined 10 classes, start
 3/ Let the Java2Demo start, switch to Methods profiling


java.lang.NullPointerException
	at org.netbeans.lib.profiler.results.cpu.CPUCallGraphBuilder.plainMethodEntry(CPUCallGraphBuilder.java:1202)
	at org.netbeans.lib.profiler.results.cpu.CPUCallGraphBuilder.plainMethodEntry(CPUCallGraphBuilder.java:1245)
	at org.netbeans.lib.profiler.results.cpu.CPUCallGraphBuilder.methodEntryUnstamped(CPUCallGraphBuilder.java:243)
	at org.netbeans.lib.profiler.results.cpu.CPUDataFrameProcessor$2.execute(CPUDataFrameProcessor.java:441)
	at org.netbeans.lib.profiler.results.AbstractDataFrameProcessor.foreachListener(AbstractDataFrameProcessor.java:177)
	at org.netbeans.lib.profiler.results.cpu.CPUDataFrameProcessor.fireMethodEntryUnstamped(CPUDataFrameProcessor.java:439)
	at org.netbeans.lib.profiler.results.cpu.CPUDataFrameProcessor.doProcessDataFrame(CPUDataFrameProcessor.java:78)
[catch] at org.netbeans.lib.profiler.results.AbstractDataFrameProcessor.processDataFrame(AbstractDataFrameProcessor.java:97)
	at org.netbeans.lib.profiler.results.ProfilingResultsDispatcher$1.run(ProfilingResultsDispatcher.java:140)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)
Comment 1 Tomas Hurka 2014-12-12 14:09:14 UTC 
*** Bug 249324 has been marked as a duplicate of this bug. ***
Comment 2 Tomas Hurka 2014-12-19 13:23:27 UTC 
*** Bug 249457 has been marked as a duplicate of this bug. ***
Comment 3 Tomas Hurka 2015-04-21 17:31:15 UTC 
From the messages.log file:

*** Profiler Engine: internal error: got unknown event type in CPUDataFrameProcessor: 0 at 102

This issue should be fixed in the latest dev. builds.