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 70301 - NPE when modifying profiling from CPU to Memory
Summary: NPE when modifying profiling from CPU to Memory
Status: VERIFIED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
: 71750 75784 80310 83327 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-12-12 23:52 UTC by Jiri Sedlacek
Modified: 2009-01-12 15:48 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
NPE during modify profiling CPU -> Memory (8.63 KB, text/plain)
2005-12-12 23:52 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 2005-12-12 23:52:11 UTC 
Profiler pre-M12, NB 5.0 beta2, Windows, AnagramGame

When modifying profiling from CPU Entire to Memory Alloc & Stack traces with 
live results on, got following NPE (attached).

On another retry modifying didn't stop and kept running unless I stopped the 
profiling session.
Comment 1 Jiri Sedlacek 2005-12-12 23:52:57 UTC 
Created attachment 27774 [details]
NPE during modify profiling CPU -> Memory
Comment 2 iformanek 2006-01-06 18:19:34 UTC 
Caused by the fact that Live results are repainting in a transition state. Live 
Results should be cleared before the instrumentation modification starts.
Comment 3 Jiri Sedlacek 2006-02-09 12:57:33 UTC 
Fixed for 5.5.
Comment 4 Jiri Sedlacek 2006-02-09 13:18:49 UTC 
*** Issue 71750 has been marked as a duplicate of this issue. ***
Comment 5 Jiri Sedlacek 2006-03-13 10:23:09 UTC 
Not for 5.5, fixed in trunk only.
Comment 6 ehucka 2006-05-02 18:36:20 UTC 
strange, I guess release55 branch was created 2/28 so the issue cannot be fixed
in trunk too
Comment 7 ehucka 2006-05-02 18:36:30 UTC 
*** Issue 75784 has been marked as a duplicate of this issue. ***
Comment 8 ehucka 2006-05-03 13:34:40 UTC 
I understood our branches structure. Is it possible to fix it in release55 branch?
Comment 9 ehucka 2006-08-31 14:26:17 UTC 
We probably forgot for this issue. It should be fixed in release 55.
Comment 10 ehucka 2006-08-31 14:27:09 UTC 
*** Issue 83327 has been marked as a duplicate of this issue. ***
Comment 11 Tomas Hurka 2006-08-31 14:56:07 UTC 
This issue is FIXED in trunk. There is no reason to reopen it, if you want to fix it in release55.
Comment 12 Jiri Sedlacek 2006-09-01 09:47:07 UTC 
Merged into release55 branch.
Comment 13 Jiri Sedlacek 2006-09-04 12:40:39 UTC 
*** Issue 80310 has been marked as a duplicate of this issue. ***
Comment 14 Rashid Urusov 2009-01-12 15:48:58 UTC 
VERIFIED in build 200901120201