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 114376 - NPE after profile with added Triggered pp
Summary: NPE after profile with added Triggered pp
Status: VERIFIED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-31 14:17 UTC by Maksim Khramov
Modified: 2007-10-09 09:47 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 Maksim Khramov 2007-08-31 14:17:54 UTC 
Product Version: NetBeans IDE Dev (Build 200708270000) 
Java: 1.6.0_02; Java HotSpot(TM) Client VM 1.6.0_02-b05 
System: Windows XP version 5.1 running on x86; Cp1251; ru_RU (nb)

Steps to reproduce:
Create AnagramGame project and perform profiling in Memory mode.
Close tested application.
Add Triggered profiling point with Loaded classes exceeds 3
Run profiling again.
The NPE is thrown:
java.lang.NullPointerException
	at java.io.DataOutputStream.writeUTF(DataOutputStream.java:330)
	at java.io.DataOutputStream.writeUTF(DataOutputStream.java:306)
	at com.sun.tools.profiler.results.memory.MemoryResultsSnapshot.writeToStream(MemoryResultsSnapshot.java:159)
	at com.sun.tools.profiler.results.memory.AllocMemoryResultsSnapshot.writeToStream(AllocMemoryResultsSnapshot.java:59)
	at org.netbeans.modules.profiler.LoadedSnapshot.save(LoadedSnapshot.java:166)
	at org.netbeans.modules.profiler.ResultsManager.saveSnapshot(ResultsManager.java:354)
	at
org.netbeans.modules.profiler.ppoints.TriggeredTakeSnapshotProfilingPoint.takeSnapshotHit(TriggeredTakeSnapshotProfilingPoint.java:234)
	at
org.netbeans.modules.profiler.ppoints.TriggeredTakeSnapshotProfilingPoint.hit(TriggeredTakeSnapshotProfilingPoint.java:211)
	at
org.netbeans.modules.profiler.ppoints.GlobalProfilingPointsProcessor.processTriggeredProfilingPoint(GlobalProfilingPointsProcessor.java:222)
	at
org.netbeans.modules.profiler.ppoints.GlobalProfilingPointsProcessor.processTriggeredProfilingPoints(GlobalProfilingPointsProcessor.java:178)
	at
org.netbeans.modules.profiler.ppoints.GlobalProfilingPointsProcessor.processTelemetryEvent(GlobalProfilingPointsProcessor.java:143)
	at
org.netbeans.modules.profiler.ppoints.GlobalProfilingPointsProcessor.dataChanged(GlobalProfilingPointsProcessor.java:285)
	at com.sun.tools.profiler.results.DataManager$1.run(DataManager.java:63)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
[catch] at java.lang.Thread.run(Thread.java:619)
Comment 1 J Bachorik 2007-08-31 14:35:40 UTC 
this is not longer reproducible on Dev Build 20070831 - there were some changes in the way the incoming results were
being handled and this seems to be fixed as a side-effect
Comment 2 Maksim Khramov 2007-10-09 09:47:36 UTC 
Verified in build 200710081200