[ BUILD # : 200710212201 ]
[ JDK VERSION : 1.6.0_03 ]
I am attaching the profiler to the target VM via local dynamic attach
If I use Memory or CPU profiling, the target VM crashes shortly after
attach or a little while later.
This also happens with VisualVM. So, it is either a profiler issue or
a JDK issue.
Attaching crash log.
Profiler Agent: JNI On Load Initializing...
Profiler Agent: JNI OnLoad Initialized succesfully
Profiler Agent: Waiting for connection on port 5140 (Protocol
Profiler Agent: Established local connection with the tool
cache_loade_classes, classes 2
Profiler Agent: Redefining 100 classes at idx 0, out of total 513
Profiler Agent: Redefining 100 classes at idx 100, out of total 513
Profiler Agent: Redefining 100 classes at idx 200, out of total 513
Profiler Agent: Redefining 100 classes at idx 300, out of total 513
Profiler Agent: Redefining 100 classes at idx 400, out of total 513
Profiler Agent: Redefining 13 classes at idx 500, out of total 513
# An unexpected error has been detected by Java Runtime Environment:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d83de95,
# Java VM: Java HotSpot(TM) Client VM (1.6.0_03-b05 mixed mode,
# Problematic frame:
# V [jvm.dll+0x7de95]
# An error report file with more information is saved as
# If you would like to submit a bug report, please visit:
Created attachment 51644 [details]
this is a duplication of the issue #88776
a known workaround is to start the profiled application with -Xshare:off argument
*** This issue has been marked as a duplicate of 88776 ***
Thanks, this works as workaround. However, CPU profiling does not work after attach. I get no live results and cannot
take snapshots. Not even for threads that are being started after attach. Is this a known problem? Shall I file a new issue?
1) Enable "Profile Threads started after entering any of root methods" Advanced Settings option
2) Open profiled application sources in NetBeans as project and select it in Attach dialog.
If this doesn't help then please file new issue.
I did: Issue #120038. And it is already fixed. :-)