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 65305 - Profiled VM death
Summary: Profiled VM death
Status: CLOSED INVALID
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 5.x
Hardware: PC Windows ME/2000
: P1 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-29 09:24 UTC by matthiasmann
Modified: 2007-02-21 10:36 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Hotspot crash report file (7.12 KB, text/plain)
2005-09-29 09:25 UTC, matthiasmann 		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 matthiasmann 2005-09-29 09:24:14 UTC 
I installed the just released Netbeans 5.0 beta and Profiler M9. I profiled my
application with the option "Apllication Performance" with "exclude Java core
classes".

I gor the following output:
init:
profile-init:
deps-jar:
compile:
profile:
Profiler Engine: waiting for connection on port 5140
Profiler Engine: local connection with the tool
D:\j2sdk\NetBeans5.0beta\.
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d6b1e27, pid=860, tid=920
#
# Java VM: Java HotSpot(TM) Client VM (1.5.0_04-b05 mixed mode)
# Problematic frame:
# V  [jvm.dll+0x1e27]
#
# An error report file with more information is saved as hs_err_pid860.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#
Agent_OnLoad called...
Agent_OnLoad completed successfully.
Profiler Agent: Thread.sleep intercepted.
Profiler Agent: Object.wait intercepted.
Java Result: 1
BUILD SUCCESSFUL (total time: 12 seconds)
Comment 1 matthiasmann 2005-09-29 09:25:45 UTC 
Created attachment 25280 [details]
Hotspot crash report file
Comment 2 matthiasmann 2005-09-29 11:35:40 UTC 
I updated my Java runtime to 1.5.0_05 which solved the crash issue.
Comment 3 ehucka 2006-10-09 12:11:57 UTC 
Verification of old issues.
Comment 4 Alexander Kouznetsov 2007-02-21 10:36:37 UTC 
Closing old issues