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

[JVMCI] thread is _thread_in_vm when committing JFR compilation event

XMLWordPrintable

    • 19
    • b12

      JDK-8280844 added a native-to-VM thread transition when committing a JFR compilation event. This is not necessary for a JVMCI compiler as it is already _thread_in_vm at the commit point. This is shown by the following assertion failure:

      # Internal Error (/b/b/e/main/jdk_tlda/open/src/hotspot/share/runtime/interfaceSupport.inline.hpp:97), pid=4974, tid=5013
      # assert(thread->thread_state() == _thread_in_native) failed: coming from wrong thread state

      Stack: [0x000014376aff6000,0x000014376b1f7000], sp=0x000014376b1f54b0, free space=2045k
      Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
      V [libjvm.so+0xb1f1a2] CompilerEvent::CompilationEvent::post(EventCompilation&, int, CompilerType, Method*, int, bool, bool, int, int)+0x192 (interfaceSupport.inline.hpp:97)
      V [libjvm.so+0xaf1ab9] post_compilation_event(EventCompilation&, CompileTask*)+0x79
      V [libjvm.so+0xafb4fd] CompileBroker::invoke_compiler_on_method(CompileTask*)+0xc7d
      V [libjvm.so+0xafc0b8] CompileBroker::compiler_thread_loop()+0x5d8
      V [libjvm.so+0x106a7c6] JavaThread::thread_main_inner()+0x206
      V [libjvm.so+0x1a6f260] Thread::call_run()+0x100
      V [libjvm.so+0x1702eb3] thread_native_entry(Thread*)+0x103

            dnsimon Douglas Simon
            dnsimon Douglas Simon
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: