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 98017 - Profiling Points behave differently in Memory and CPU mode
Summary: Profiling Points behave differently in Memory and CPU mode
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-03-15 17:32 UTC by Alexander Kouznetsov
Modified: 2007-05-10 16:30 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 Alexander Kouznetsov 2007-03-15 17:32:28 UTC
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:
- Open Anagrams.java of Anagram Game Sample Application
- Select guessedWordActionPerformed() method body including closing curled brace
"}" in the end
- Right-click and select Insert Profiling Point
- Select Stopwatch. Next. Finish.
- Run Analyze Performance profiling (Entire Application, Profile Only Project
Classes)
- Press Guess button several times.
- Open PP report and verify that both timestamps and duration are shown for each hit
- Run Analyze Memory profiling (Record only Object Creation, 10 Allocations,
stack trace disabled)
- Press Guess button several times.
- Open PP report
- RESULT: Snapshots are shown, but duration is not shown as "pending".
Comment 1 Jiri Sedlacek 2007-03-22 17:52:58 UTC
Seems to work correctly in latest build, closing as fixed.
Comment 2 Alexander Kouznetsov 2007-05-10 16:30:43 UTC
Verified with
Profiler 070509
NetBeans IDE Dev (Build 070509)
1.6.0; Java HotSpot(TM) Client VM 1.6.0-b105
Windows XP version 5.1 running on x86
ru_RU (nb); Cp1251