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 49053 - JVM crashes when showing "Stack traces for allocations"
Summary: JVM crashes when showing "Stack traces for allocations"
Status: CLOSED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 4.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: mishadmitriev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-15 09:34 UTC by Jiri Sedlacek
Modified: 2007-02-20 18:25 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
jvm log file. (5.89 KB, text/plain)
2004-09-24 20:25 UTC, ciliberton 		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 2004-09-15 09:34:44 UTC 
When profiling Memory usage (both object creation 
and object creation with garbage collection), I 
press the "Get current results" button, stop the 
JVM by the "Stop" button and try to show stack 
traces for allocations by doubleclicking on some 
table row. The "Target JVM inactive" dialog shows.
OK, I press the "ReRun last profiling" button, 
request current results and doubleclick on a 
table row (without stopping the JVM). The JVM 
crashes and "Target JVM inactive" dialog shows 
again. I must restart NetBeans to get the "Show 
stack traces for allocations" working again.
Comment 1 ciliberton 2004-09-21 21:04:59 UTC 
I have a similar problem.  I can do it for allocations that are 
small, but when I do it for large byte arrays (~13MB) it shutsdown 
the _target_ jvm.  It doesn't cause the profiler to stop.  I'm using 
Sun's jvm build 1.4.2_05-b04.
Comment 2 mishadmitriev 2004-09-24 16:05:48 UTC 
Fixed, code will become available in Milestone 2 release due in the 
beginning of October'04
Comment 3 ciliberton 2004-09-24 20:25:30 UTC 
Created attachment 17865 [details]
jvm log file.
Comment 4 ehucka 2006-10-09 12:11:58 UTC 
Verification of old issues.
Comment 5 Alexander Kouznetsov 2007-02-12 22:58:26 UTC 
Closing old issues.
Comment 6 Alexander Kouznetsov 2007-02-20 18:25:58 UTC 
Reverting to the original Target Milestone value changed by mistake. Sorry for
inconvenience.