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

JVMCI: SIGSEGV in ObjectMonitor::enter

    Details

    • Subcomponent:
    • CPU:
      x86_64
    • OS:
      linux

      Description

      The following test failed in the JDK16 CI:

      applications/dacapo/Dacapo24H.java

      Here's a snippet from the log file:

      Output and diagnostic info for process 29809 was saved into 'pid-29809-output.log'
      [2020-07-07T16:50:02.248072455Z] Gathering output for process 29812
      [2020-07-07T16:50:08.452303287Z] Waiting for completion for process 29812
      [2020-07-07T16:50:08.452384558Z] Waiting for completion finished for process 29812
      Output and diagnostic info for process 29812 was saved into 'pid-29812-output.log'
      [stress.process.out] #
      [stress.process.out] # A fatal error has been detected by the Java Runtime Environment:
      [stress.process.out] #
      [stress.process.out] # SIGSEGV (0xb) at pc=0x00007fc485ed0c3b, pid=27972, tid=27994
      [stress.process.out] #
      [stress.process.out] # JRE version: Java(TM) SE Runtime Environment (16.0+5) (build 16-ea+5-144)
      [stress.process.out] # Java VM: Java HotSpot(TM) 64-Bit Server VM (16-ea+5-144, mixed mode, sharing, tiered, jvmci, jvmci compiler, compressed oops, g1 gc, linux-amd64)
      [stress.process.out] # Problematic frame:
      [stress.process.out] # V [libjvm.so+0xb2dc3b][thread 28003 also had an error][thread 28033 also had an error][thread 19513 also had an error]
      [stress.process.out]
      [stress.process.out]
      [stress.process.out] [thread 29735 also had an error]
      [stress.process.out] ObjectMonitor::enter(Thread*)+0x26b
      [stress.process.out] #
      [stress.process.out] # Core dump will be written. Default location: Core dumps may be processed with "/opt/core.sh %p" (or dumping to /opt/mach5/mesos/work_dir/slaves/4728e7c1-7e67-490e-be0f-6bbf2a2f33db-S312/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/071c18ec-8a9f-4eff-b967-760656fc6748/runs/14bed3b8-d48a-4534-8d64-9b05c8bff8c7/testoutput/test-support/jtreg_closed_test_hotspot_jtreg_applications_dacapo_Dacapo24H_java/scratch/0/core.27972)
      [stress.process.out] #
      [stress.process.out] # JFR recording file will be written. Location: /opt/mach5/mesos/work_dir/slaves/4728e7c1-7e67-490e-be0f-6bbf2a2f33db-S312/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/071c18ec-8a9f-4eff-b967-760656fc6748/runs/14bed3b8-d48a-4534-8d64-9b05c8bff8c7/testoutput/test-support/jtreg_closed_test_hotspot_jtreg_applications_dacapo_Dacapo24H_java/scratch/0/hs_err_pid27972.jfr
      [stress.process.out] #
      [stress.process.out] Unsupported internal testing APIs have been used.
      [stress.process.out]
      [stress.process.out] # An error report file with more information is saved as:
      [stress.process.out] # /opt/mach5/mesos/work_dir/slaves/4728e7c1-7e67-490e-be0f-6bbf2a2f33db-S312/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/071c18ec-8a9f-4eff-b967-760656fc6748/runs/14bed3b8-d48a-4534-8d64-9b05c8bff8c7/testoutput/test-support/jtreg_closed_test_hotspot_jtreg_applications_dacapo_Dacapo24H_java/scratch/0/hs_err_pid27972.log
      [2020-07-07T16:51:08.456860043Z] Gathering output for process 30000
      [2020-07-07T16:51:08.467649348Z] Waiting for completion for process 30000
      [2020-07-07T16:51:08.467716687Z] Waiting for completion finished for process 30000
      Output and diagnostic info for process 30000 was saved into 'pid-30000-output.log'
      [2020-07-07T16:51:08.470329392Z] Gathering output for process 30004
      [2020-07-07T16:51:14.660302539Z] Waiting for completion for process 30004
      [2020-07-07T16:51:14.660484951Z] Waiting for completion finished for process 30004
      Output and diagnostic info for process 30004 was saved into 'pid-30004-output.log'
      [2020-07-07T16:52:14.664684358Z] Gathering output for process 30103
      [2020-07-07T16:52:14.674857347Z] Waiting for completion for process 30103
      [2020-07-07T16:52:14.674908314Z] Waiting for completion finished for process 30103
      Output and diagnostic info for process 30103 was saved into 'pid-30103-output.log'
      [2020-07-07T16:52:14.677491502Z] Gathering output for process 30107
      [2020-07-07T16:52:20.866363883Z] Waiting for completion for process 30107
      [2020-07-07T16:52:20.866458289Z] Waiting for completion finished for process 30107
      Output and diagnostic info for process 30107 was saved into 'pid-30107-output.log'
      [stress.process.out]
      [stress.process.out] ------ Timeout during error reporting after 120 s. ------

      Here's the crashing thread's stack:

      --------------- T H R E A D ---------------

      Current thread (0x00007fc48019edd0): JavaThread "Finalizer" daemon [_thread_in_vm, id=27994, stack(0x00007fc41c2b3000,0x00007fc41c3b4000)]

      Stack: [0x00007fc41c2b3000,0x00007fc41c3b4000], sp=0x00007fc41c3b2520, free space=1021k
      Native frames: (J=compiled Java code, A=aot compiled Java code, j=interpreted, Vv=VM code, C=native code)
      V [libjvm.so+0xb2dc3b] ObjectMonitor::enter(Thread*)+0x26b
      V [libjvm.so+0xca613c] ObjectSynchronizer::enter(Handle, BasicLock*, Thread*)+0xcc
      V [libjvm.so+0xc06853] SharedRuntime::monitor_enter_helper(oopDesc*, BasicLock*, JavaThread*)+0x63
      V [libjvm.so+0x8f8bba] JVMCIRuntime::monitorenter(JavaThread*, oopDesc*, BasicLock*)+0x1a
      v ~RuntimeStub::Stub<monitorenter(Object,Word)void>
      J 8127690 jvmci java.nio.channels.spi.AbstractInterruptibleChannel.close()V java.base@16-ea (37 bytes) @ 0x00007fc46ef4352a [0x00007fc46ef43300+0x000000000000022a]
      J 8121297 c1 jdk.nio.zipfs.ZipFileSystem.close()V jdk.zipfs@16-ea (390 bytes) @ 0x00007fc468ba7aa4 [0x00007fc468ba7600+0x00000000000004a4]
      J 8121292 c1 jdk.nio.zipfs.ZipFileSystem.finalize()V jdk.zipfs@16-ea (5 bytes) @ 0x00007fc468ba4404 [0x00007fc468ba43a0+0x0000000000000064]
      J 8125623 jvmci java.lang.ref.Finalizer.runFinalizer(Ljdk/internal/access/JavaLangAccess;)V java.base@16-ea (117 bytes) @ 0x00007fc46e7a8e0d [0x00007fc46e7a8760+0x00000000000006ad]
      J 8125624% jvmci java.lang.ref.Finalizer$FinalizerThread.run()V java.base@16-ea (56 bytes) @ 0x00007fc4708e5dcc [0x00007fc4708e5be0+0x00000000000001ec]
      v ~StubRoutines::call_stub
      V [libjvm.so+0x771fb9] JavaCalls::call_helper(JavaValue*, methodHandle const&, JavaCallArguments*, Thread*)+0x299
      V [libjvm.so+0x77389b] JavaCalls::call_virtual(JavaValue*, Handle, Klass*, Symbol*, Symbol*, Thread*)+0x1cb
      V [libjvm.so+0x82e06d] thread_entry(JavaThread*, Thread*)+0x6d
      V [libjvm.so+0xcfb93e] JavaThread::thread_main_inner()+0xde
      V [libjvm.so+0xd0078d] Thread::call_run()+0xfd
      V [libjvm.so+0xb53b37] thread_native_entry(Thread*)+0xe7

      Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
      v ~RuntimeStub::Stub<monitorenter(Object,Word)void>
      J 8127690 jvmci java.nio.channels.spi.AbstractInterruptibleChannel.close()V java.base@16-ea (37 bytes) @ 0x00007fc46ef4352a [0x00007fc46ef43300+0x000000000000022a]
      J 8121297 c1 jdk.nio.zipfs.ZipFileSystem.close()V jdk.zipfs@16-ea (390 bytes) @ 0x00007fc468ba7aa4 [0x00007fc468ba7600+0x00000000000004a4]
      J 8121292 c1 jdk.nio.zipfs.ZipFileSystem.finalize()V jdk.zipfs@16-ea (5 bytes) @ 0x00007fc468ba4404 [0x00007fc468ba43a0+0x0000000000000064]
      J 8125623 jvmci java.lang.ref.Finalizer.runFinalizer(Ljdk/internal/access/JavaLangAccess;)V java.base@16-ea (117 bytes) @ 0x00007fc46e7a8e0d [0x00007fc46e7a8760+0x00000000000006ad]
      J 8125624% jvmci java.lang.ref.Finalizer$FinalizerThread.run()V java.base@16-ea (56 bytes) @ 0x00007fc4708e5dcc [0x00007fc4708e5be0+0x00000000000001ec]
      v ~StubRoutines::call_stub

      siginfo: si_signo: 11 (SIGSEGV), si_code: 128 (SI_KERNEL), si_addr: 0x0000000000000000


      Please note that this failure mode is NOT a duplicate of:

          JDK-8248438 SIGSEGV in ObjectMonitor::enter

      That bug was resolved by backing out JDK-8244603.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                yzheng Yudi Zheng
                Reporter:
                dcubed Daniel Daugherty
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: