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 77542 - NPE while running with Profiling Points
Summary: NPE while running with Profiling Points
Status: VERIFIED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
: 77466 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-06-07 21:10 UTC by _ gsporar
Modified: 2007-09-24 14:45 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
sample application, in a project (42.10 KB, application/octet-stream)
2006-06-07 21:10 UTC, _ gsporar 		Details
message log (17.22 KB, text/plain)
2006-06-07 21:11 UTC, _ gsporar 		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 _ gsporar 2006-06-07 21:10:28 UTC 
This is probably the same problem as I reported in
http://www.netbeans.org/issues/show_bug.cgi?id=77466, but just in case it is not
I am opening a new IZ.  The behavior is slightly different and I have changed
the sample application.  The new version of the sample application is attached
to this IZ, along with the message log.

I'll put the steps to reproduce in a separate comment.
Comment 1 _ gsporar 2006-06-07 21:10:58 UTC 
Created attachment 30869 [details]
sample application, in a project
Comment 2 _ gsporar 2006-06-07 21:11:37 UTC 
Created attachment 30870 [details]
message log
Comment 3 _ gsporar 2006-06-07 21:17:06 UTC 

1. Put a Reset Results Profiling Point on line 31 of PrimeCalculator.java
2. Put a Take Snapshot Profiling Point on line 63 of PrimeCalculator.java
3. Profile the application, choosing Analyze Performance with "Entire
Application" and "Profile All Classes" selected.
4. When the app. starts, put in a number that is less than 100000 and click the
button.  

The application starts to eat up CPU time (which is expected) and then I see the
NPE dialog box (the NPE stack trace is in the attached log file).

After I dismiss the dialog box I cannot end my application.  The IDE sometimes
hangs as well, I typically end up using the Task Manager to kill both the IDE
and my application.
Comment 4 Maros Sandor 2006-06-12 14:47:07 UTC 
It seems the Reset point confuses profiler if results are reset inside call
graph, needs more investigation.
Comment 5 Maros Sandor 2006-06-12 16:00:39 UTC 
*** Issue 77466 has been marked as a duplicate of this issue. ***
Comment 6 Maros Sandor 2006-06-13 13:11:57 UTC 
Internal processing of profiling points was defective. #95631
Comment 7 Alexander Kouznetsov 2007-09-24 14:45:50 UTC 
Verified with 200709200000