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 232972 - Snapshot taken twice at profiling point
Summary: Snapshot taken twice at profiling point
Status: VERIFIED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Engine (show other bugs)
Version: 7.4
Hardware: All All
: P3 normal (vote)
Assignee: Tomas Hurka
URL:
Keywords: REGRESSION
Depends on:
Blocks:
 
Reported: 2013-07-18 10:41 UTC by Jiri Skrivanek
Modified: 2013-07-29 09:00 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 Jiri Skrivanek 2013-07-18 10:41:32 UTC 
When profiling point is defined it takes cpu snapshot twice

Stopwatch profiling point does produce any results and CNFE is thrown in console. To reproduce:

- create project "Samples|Java|Anagram Game"
- open Anagrams.java
- right-click at line 251 and choose "Profiling|insert Profiling Point..."
- select "Take Snapshot" and click Next
- click Finish
- right-click AnagramGame project node and choose "Profile"
- select "CPU|Analyze Performance|Advanced|Profile only project classes", check "Use defined profiling points" and click Run
- click "New Word" button and there appears two new cpu snapshots in "Saved Snapshots"

Product Version: NetBeans IDE Dev (Build 201307172300)
Java: 1.7.0_40-ea; Java HotSpot(TM) 64-Bit Server VM 24.0-b53
Runtime: Java(TM) SE Runtime Environment 1.7.0_40-ea-b34
System: Windows 7 version 6.1 running on amd64; Cp1250; en_US (nb)
Comment 1 Jiri Sedlacek 2013-07-22 12:43:08 UTC 
o.n.lib.profiler.results.AbstractDataFrameProcessor.fireProfilingPoint(...) - two listeners registered: CPUCallGraphBuilder and LockGraphBuilder$CPULockGraphBuilder, causes firing two events for one profiling point hit.
Comment 2 Tomas Hurka 2013-07-23 07:59:02 UTC 
This is caused by introduction of lock contention monitoring.
Comment 3 Tomas Hurka 2013-07-23 16:00:49 UTC 
Fixed in profiler-main

changeset:   259052:7f65672757db
user:        Tomas Hurka <thurka@netbeans.org>
date:        Tue Jul 23 17:10:23 2013 +0200
summary:     bugfix #231428, implement profilingPoint() in subclasses; implementation in LockGraphBuilder does nothing