Java process crashed when some unknown code tried to attach current thread through jni_AttachCurrentThread or attach_current_thread function.

Solution Unverified - Updated -

Issue

A Java process crashed when some unknown code tried to attach current thread through jni_AttachCurrentThread (*1-1) or attach_current_thread (*1-2) function in JVM.

(*1) Excerpt from hs_err_pid<pid>.log

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007ffff660ed98, pid=1129201, tid=1129214
#
# JRE version: OpenJDK Runtime Environment (Red_Hat-17.0.8.0.7-1) (17.0.8+7) (build 17.0.8+7-LTS)
# Java VM: OpenJDK 64-Bit Server VM (Red_Hat-17.0.8.0.7-1) (17.0.8+7-LTS, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# V  [libjvm.so+0x825d98]  InstanceKlass::allocate_instance_handle(JavaThread*)+0x18
#
    :
    :
Current thread (0x00007fffbc000bc0):  JavaThread "Unknown thread" [_thread_in_vm, id=1129214, stack(0x00007fffc5801000,0x00007fffc6000000)]

Stack: [0x00007fffc5801000,0x00007fffc6000000],  sp=0x00007fffc5ffecd0,  free space=8183k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V  [libjvm.so+0x825d98]  InstanceKlass::allocate_instance_handle(JavaThread*)+0x18
V  [libjvm.so+0xefd0ad]  JavaThread::allocate_threadObj(Handle, char const*, bool, JavaThread*)+0x4d
V  [libjvm.so+0x8e7180]  attach_current_thread.part.298+0x160    <---------- (*1-2)
V  [libjvm.so+0x8e73ed]  jni_AttachCurrentThread+0x6d            <---------- (*1-1)
C  0x00007fffd470e654
C  0x00007fffd470e932
    :
    :

Environment

  • OpenJDK
    • 17
  • Red Hat Enterprise Linux

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content