JVM crash with YourKit 2013

[hagis]

Hi,

We often keep YourKit enabled on our Webapp servers just in case we want to take a peek at what is happening inside.

Yesterday, however, we had one of our Webapp servers die on us after running less than 2 hours with profiling enabled but no profiler connected.

The JVM death dump file highlights:
Current thread (0x00007fe32c6af800): JavaThread "YJPAgent-Telemetry" daemon [_thread_in_native, id=20546, stack(0x00007fe327335000,0x00007fe327436000)]
Heap used less than 100 MB
PermGen used less than 100 MB
vm_info: OpenJDK 64-Bit Server VM (24.45-b08)
Memory: 4k page, physical 1922428k(121748k free), swap 2097144k(2093800k free)
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j com.yourkit.runtime.Callback.isFrequentSampling()Z+0
J com.yourkit.runtime.TelemetryThread.run()V
v ~StubRoutines::call_stub

So, JVM or system memory does not seem to be the issue.

YourKit log file does not show anything suspicious, though I'm no expert on that.

JVM death dump, yourkit log and core dump file are available at request.

[Anton Katilin]

Hi,

JVM death dump, yourkit log and core dump file are available at request.

Could you please send them to [email protected]

Best regards,
Anton

[Paul Gazda]

We also had a crash of Yourkit 2013 (build 13074) on Mar 27, 2014 while it was running on the server but not actively connected. The thread at time of crash was not yourkit, but yourkit was near the top of the stack trace.

# JRE version: 7.0_25-b15
# Java VM: Java HotSpot(TM) 64-Bit Server VM (23.25-b01 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# V [libjvm.so+0x63593e] JvmtiTagMap::create_entry(oopDesc*, long)+0x2e

Stack: [0x00002b50e7e3e000,0x00002b50e7f3f000], sp=0x00002b50e7f38840, free space=1002k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [libjvm.so+0x63593e] JvmtiTagMap::create_entry(oopDesc*, long)+0x2e
V [libjvm.so+0x63869e] JvmtiTagMap::set_tag(_jobject*, long)+0x1ae
V [libjvm.so+0x603795] JvmtiEnv::SetTag(_jobject*, long)+0x45
V [libjvm.so+0x5bface] jvmti_SetTag+0x22e
C [libyjpagent.so+0xc4cdc] Java_com_yourkit_runtime_Callback_objectGetID+0x7c

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
J com.yourkit.runtime.Callback.objectGetID(Ljava/lang/Object;)J
j com.yourkit.probes.ResourceCounter.open(Ljava/lang/Object;Ljava/lang/String;)V+22
j com.yourkit.probes.builtin.DatabasesLW$DataSource_getConnection_Probe.onReturn(Ljavax/sql/DataSource;Ljava/sql/Connection;)V+48

[Anton Katilin]

Hello Paul

It's a crash in JVM code. It might have been caused by a lack of memory (which is unlikely because it was a 64-bit JVM) or an unknown JVM bug.

If possible, could you please provide the hs_err log file content in full; perhaps we'll be able to tell more about the crash.

Also, it's always recommended to upgrade to the latest Java update. You used Java 7 update 25, while update 55 is available at the moment.

Best regards,
Anton