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 232978 - Timed Profiling Point still active after deletion
Summary: Timed Profiling Point still active after deletion
Status: VERIFIED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 7.4
Hardware: All All
: P3 normal (vote)
Assignee: Jiri Sedlacek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-18 11:37 UTC by Jiri Skrivanek
Modified: 2013-07-25 06:59 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Skrivanek 2013-07-18 11:37:17 UTC
Timed Profiling Point is still active even it is deleted. To reproduce:

- create project "Samples|Java|Anagram Game"
- open Anagrams.java
- right-click at line 251 and choose "Profiling|Insert Profiling Point..."
- select "Timed Take Snapshot" and click Next
- select "Take every" and ensure 1 minute is set
- click OK
- start profiling (CPU/Advanced) and wait until snapshot appears in Saved Snapshots
- stop profiling
- go Profiling Points window and delete profiling point
- start profiling again and in every minute one new snapshot is added

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 13:55:09 UTC
Fixed by http://hg.netbeans.org/profiler-main/rev/860d11fe549e.
Comment 2 Quality Engineering 2013-07-25 02:28:56 UTC
Integrated into 'main-silver', will be available in build *201307242300* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)

Changeset: http://hg.netbeans.org/main-silver/rev/860d11fe549e
User: Jiri Sedlacek <jis@netbeans.org>
Log: Bugfix #232978 - init global profiling points after resetting ProfilingPointsManager on new profiling session