Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8065346

WB_AddToBootstrapClassLoaderSearch calls JvmtiEnv::create_a_jvmti when not in _thread_in_vm state

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: P1 P1
    • 9
    • 9
    • hotspot
    • b42
    • Verified

        JDK-8064701 added the function WB_AddToBootstrapClassLoaderSearch. This function calls JvmtiEnv::create_a_jvmti() while the thread is in "native" state. JvmtiEnv::create_a_jvmti() requires the thread to be in "vm" state.

        This results in an assert:

        #
        # A fatal error has been detected by the Java Runtime Environment:
        #
        # Internal Error (/opt/jprt/T/P1/005732.iklam/s/hotspot/src/share/vm/runtime/mutex.cpp:1367), pid=15057, tid=140678647793408
        # assert((!thread->is_Java_thread() || ((JavaThread *)thread)->thread_state() == _thread_in_vm) || rank() == Mutex::special) failed: wrong thread state for using locks
        #
        # JRE version: Java(TM) SE Runtime Environment (9.0) (build 1.9.0-internal-fastdebug-201411190057.iklam.jdk9-b00)
        # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.9.0-internal-fastdebug-201411190057.iklam.jdk9-b00 compiled mode, sharing linux-amd64 compressed oops)
        # Core dump written. Default location: /export/local/aurora/sandbox/results/workDir/closed/runtime/AppCDS/JvmtiAddPath/core or core.15057
        #
        # If you would like to submit a bug report, please visit:
        # http://bugreport.java.com/bugreport/crash.jsp
        # The crash happened outside the Java Virtual Machine in native code.
        # See problematic frame for where to report the bug.
        #


              iklam Ioi Lam
              sla Staffan Larsen (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: