-
Bug
-
Resolution: Fixed
-
P4
-
repo-loom
Test
serviceability/jvmti/events/MonitorContendedEntered/mcontentered01/mcontentered01.java
fails with
Timeout: 60000 msc
Timeout = 60000 msc.
Remembering global reference for monitor object is 0x7f21bca11508
Synchronization point checkStatus(0) called.
Data 0x7f21d801a2a8 0x7f21d801a5a0
Prepare: find tested thread
MonitorContendedEnter event:
thread: 0x7f2168000de8, object: 0x7f2168000df0, expected object: 0x7f21d849bac8
Thread: 0x7f2168000de8, name: Debuggee Thread, state(401): ALIVE BLOCKED_ON_MONITOR_ENTER, attrs: kernel
Increasing eventCount to 1
Thread started
MonitorContendedEntered event:
thread: 0x7f2168000de8, object: 0x7f2168000df0, expected object: 0x7f21d849bac8
Thread: 0x7f2168000de8, name: Debuggee Thread, state(5): ALIVE RUNNABLE, attrs: kernel
Increasing eventCount to 2
Sync: thread finished
Synchronization point checkStatus(0) called.
Data 0x7f21d801a2a8 0x7f21d801a5a0
Number of MonitorContendedEntered events: 2
MonitorContendedEnter event:
thread: 0x7f21d848ff88, object: 0x7f21d848ff90, expected object: 0x7f21d849bac8
Thread: 0x7f21d848ff88, name: main, state(401): ALIVE BLOCKED_ON_MONITOR_ENTER, attrs: kernel
# To suppress the following error report, specify this argument
# after -XX: or in .hotspotrc: SuppressErrorAt=/jniHandles.inline.hpp:64
#
# A fatal error has been detected by the Java Runtime Environment:
#
# Internal Error (/opt/mach5/mesos/work_dir/slaves/779adf21-f3e5-4e6a-a889-8cc0f9bc6fbb-S14747/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/4ceff4c0-ff1e-4329-9c88-90f77211fe28/runs/480df0be-42f1-45f1-add5-989e159fadb3/workspace/open/src/hotspot/share/runtime/jniHandles.inline.hpp:64), pid=15533, tid=15535
# assert(external_guard || result != __null) failed: Invalid JNI handle
#
# JRE version: Java(TM) SE Runtime Environment (19.0+6) (fastdebug build 19-loom+6-430)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (fastdebug 19-loom+6-430, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# V [libjvm.so+0x10dacbc] jni_IsSameObject+0x48c
#
# 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/779adf21-f3e5-4e6a-a889-8cc0f9bc6fbb-S14506/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/b72a2a64-ab38-45dd-b8e1-f80f5394205a/runs/fd75d866-ea55-4e37-9fef-48584165a02a/testoutput/test-support/jtreg_open_test_hotspot_jtreg_hotspot_serviceability/scratch/5/core.15533)
#
# An error report file with more information is saved as:
# /opt/mach5/mesos/work_dir/slaves/779adf21-f3e5-4e6a-a889-8cc0f9bc6fbb-S14506/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/b72a2a64-ab38-45dd-b8e1-f80f5394205a/runs/fd75d866-ea55-4e37-9fef-48584165a02a/testoutput/test-support/jtreg_open_test_hotspot_jtreg_hotspot_serviceability/scratch/5/hs_err_pid15533.log
#
# If you would like to submit a bug report, please visit:
# https://bugreport.java.com/bugreport/crash.jsp
#
serviceability/jvmti/events/MonitorContendedEntered/mcontentered01/mcontentered01.java
fails with
Timeout: 60000 msc
Timeout = 60000 msc.
Remembering global reference for monitor object is 0x7f21bca11508
Synchronization point checkStatus(0) called.
Data 0x7f21d801a2a8 0x7f21d801a5a0
Prepare: find tested thread
MonitorContendedEnter event:
thread: 0x7f2168000de8, object: 0x7f2168000df0, expected object: 0x7f21d849bac8
Thread: 0x7f2168000de8, name: Debuggee Thread, state(401): ALIVE BLOCKED_ON_MONITOR_ENTER, attrs: kernel
Increasing eventCount to 1
Thread started
MonitorContendedEntered event:
thread: 0x7f2168000de8, object: 0x7f2168000df0, expected object: 0x7f21d849bac8
Thread: 0x7f2168000de8, name: Debuggee Thread, state(5): ALIVE RUNNABLE, attrs: kernel
Increasing eventCount to 2
Sync: thread finished
Synchronization point checkStatus(0) called.
Data 0x7f21d801a2a8 0x7f21d801a5a0
Number of MonitorContendedEntered events: 2
MonitorContendedEnter event:
thread: 0x7f21d848ff88, object: 0x7f21d848ff90, expected object: 0x7f21d849bac8
Thread: 0x7f21d848ff88, name: main, state(401): ALIVE BLOCKED_ON_MONITOR_ENTER, attrs: kernel
# To suppress the following error report, specify this argument
# after -XX: or in .hotspotrc: SuppressErrorAt=/jniHandles.inline.hpp:64
#
# A fatal error has been detected by the Java Runtime Environment:
#
# Internal Error (/opt/mach5/mesos/work_dir/slaves/779adf21-f3e5-4e6a-a889-8cc0f9bc6fbb-S14747/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/4ceff4c0-ff1e-4329-9c88-90f77211fe28/runs/480df0be-42f1-45f1-add5-989e159fadb3/workspace/open/src/hotspot/share/runtime/jniHandles.inline.hpp:64), pid=15533, tid=15535
# assert(external_guard || result != __null) failed: Invalid JNI handle
#
# JRE version: Java(TM) SE Runtime Environment (19.0+6) (fastdebug build 19-loom+6-430)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (fastdebug 19-loom+6-430, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# V [libjvm.so+0x10dacbc] jni_IsSameObject+0x48c
#
# 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/779adf21-f3e5-4e6a-a889-8cc0f9bc6fbb-S14506/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/b72a2a64-ab38-45dd-b8e1-f80f5394205a/runs/fd75d866-ea55-4e37-9fef-48584165a02a/testoutput/test-support/jtreg_open_test_hotspot_jtreg_hotspot_serviceability/scratch/5/core.15533)
#
# An error report file with more information is saved as:
# /opt/mach5/mesos/work_dir/slaves/779adf21-f3e5-4e6a-a889-8cc0f9bc6fbb-S14506/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/b72a2a64-ab38-45dd-b8e1-f80f5394205a/runs/fd75d866-ea55-4e37-9fef-48584165a02a/testoutput/test-support/jtreg_open_test_hotspot_jtreg_hotspot_serviceability/scratch/5/hs_err_pid15533.log
#
# If you would like to submit a bug report, please visit:
# https://bugreport.java.com/bugreport/crash.jsp
#
- links to
-
Commit openjdk/loom/e8a39043