The following test crashed in the JDK26 CI:

applications/runthese/RunThese30M.java

Here's a snippet from the log file:

[2025-06-12T12:53:22.848366900Z] Gathering output for process 16940
[2025-06-12T12:53:23.455374100Z] Waiting for completion for process 16940
[2025-06-12T12:53:23.493390400Z] Waiting for completion finished for process 16940
[stress.process.out] #
[stress.process.out] # A fatal error has been detected by the Java Runtime Environment:
[stress.process.out] #
[stress.process.out] # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffad3a2c337, pid=32452, tid=56264
[stress.process.out] #
[stress.process.out] # JRE version: Java(TM) SE Runtime Environment (26.0+2) (fastdebug build 26-ea+2-98)
[stress.process.out] # Java VM: Java HotSpot(TM) 64-Bit Server VM (fastdebug 26-ea+2-98, mixed mode, tiered, compressed class ptrs, z gc, windows-amd64)
[stress.process.out] # Problematic frame:
[stress.process.out] # V [jvm.dll+0xb8c337] JvmtiBreakpoints::clearall_in_class_at_safepoint+0x97
[stress.process.out] #
[stress.process.out] # Core dump will be written. Default location: C:\\sb\\prod\\1749729503\\testoutput\\test-support\\jtreg_closed_test_hotspot_jtreg_applications_runthese_RunThese30M_java\\scratch\\0\\hs_err_pid32452.mdmp
[stress.process.out] #
[stress.process.out] # JFR recording file will be written. Location: C:\\sb\\prod\\1749729503\\testoutput\\test-support\\jtreg_closed_test_hotspot_jtreg_applications_runthese_RunThese30M_java\\scratch\\0\\hs_err_pid32452.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] # C:\\sb\\prod\\1749729503\\testoutput\\test-support\\jtreg_closed_test_hotspot_jtreg_applications_runthese_RunThese30M_java\\scratch\\0\\hs_err_pid32452.log
[stress.process.out]
[stress.process.out] [error occurred during error reporting (), id 0xe0000000, Internal Error (c:\\sb\\prod\\1749716898\\workspace\\open\\src\\hotspot\\share\\runtime\\mutex.cpp:57)]
[stress.process.out] #
[stress.process.out] # If you would like to submit a bug report, please visit:
[stress.process.out] # https://bugreport.java.com/bugreport/crash.jsp
[stress.process.out] #
[2025-06-12T12:57:38.549416900Z] Gathering output for process 39016
[2025-06-12T12:57:39.485370600Z] Waiting for completion for process 39016
[2025-06-12T12:57:39.485370600Z] Waiting for completion finished for process 39016


Stress process failed. See stress.process.err/stress.process.out files for details. The tail of stress stdout is:


The tail of stress stderr is:
vsnprintf output truncated -- buffer length is 2000 bytes but 3970 bytes are needed.
Java HotSpot(TM) 64-Bit Server VM warning: outputStream::do_vsnprintf output truncated -- buffer length is 2000 bytes but 4649 bytes are needed.
Java HotSpot(TM) 64-Bit Server VM warning: outputStream::do_vsnprintf output truncated -- buffer length is 2000 bytes but 4019 bytes are needed.
Java HotSpot(TM) 64-Bit Server VM warning: outputStream::do_vsnprintf output truncated -- buffer length is 2000 bytes but 3988 bytes are needed.

<snip>

Java HotSpot(TM) 64-Bit Server VM warning: outputStream::do_vsnprintf output truncated -- buffer length is 2000 bytes but 4397 bytes are needed.
Java HotSpot(TM) 64-Bit Server VM warning: outputStream::do_vsnprintf output truncated -- buffer length is 2000 bytes but 4366 bytes are needed.
Java HotSpot(TM) 64-Bit Server VM warning: outputStream::do_vsnprintf output truncated -- buffer length is 2000 bytes but 4415 bytes are needed.
Iteration start: ThreadDumper at Thu Jun 12 12:53:03 UTC 2025
Iteration done: ThreadDumper at Thu Jun 12 12:53:03 UTC 2025
Java HotSpot(TM) 64-Bit Server VM warning: outputStream::do_vsnprintf output truncated -- buffer length is 2000 bytes but 2867 bytes are needed.
Iteration start: Jvmti at Thu Jun 12 12:53:51 UTC 2025
Iteration start: Instrumentation at Thu Jun 12 12:53:57 UTC 2025
# [ timer expired, abort... ]

<snip>

[1582.291s][error][jvmti ] Posting Resource Exhausted event: Requested array size exceeds VM limit
[1607.104s][error][jvmti ] Posting Resource Exhausted event: Requested array size exceeds VM limit
[1688.039s][error][jvmti ] Posting Resource Exhausted event: Requested array size exceeds VM limit
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffad3a2c337, pid=32452, tid=56264
#
# JRE version: Java(TM) SE Runtime Environment (26.0+2) (fastdebug build 26-ea+2-98)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (fastdebug 26-ea+2-98, mixed mode, tiered, compressed class ptrs, z gc, windows-amd64)
# Problematic frame:
# V [jvm.dll+0xb8c337] JvmtiBreakpoints::clearall_in_class_at_safepoint+0x97
#
# Core dump will be written. Default location: C:\\sb\\prod\\1749729503\\testoutput\\test-support\\jtreg_closed_test_hotspot_jtreg_applications_runthese_RunThese30M_java\\scratch\\0\\hs_err_pid32452.mdmp
#
# JFR recording file will be written. Location: C:\\sb\\prod\\1749729503\\testoutput\\test-support\\jtreg_closed_test_hotspot_jtreg_applications_runthese_RunThese30M_java\\scratch\\0\\hs_err_pid32452.jfr
#
Unsupported internal testing APIs have been used.

# An error report file with more information is saved as:
# C:\\sb\\prod\\1749729503\\testoutput\\test-support\\jtreg_closed_test_hotspot_jtreg_applications_runthese_RunThese30M_java\\scratch\\0\\hs_err_pid32452.log

[error occurred during error reporting (), id 0xe0000000, Internal Error (c:\\sb\\prod\\1749716898\\workspace\\open\\src\\hotspot\\share\\runtime\\mutex.cpp:57)]
#
# If you would like to submit a bug report, please visit:
# https://bugreport.java.com/bugreport/crash.jsp
#
----------System.err:(498/72432)*----------

Here's the crashing thread's stack:

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

Current thread (0x000002b3185db600): VMThread "VM Thread" [id=56264, stack(0x000000e205200000,0x000000e205300000) (1024K)]

Stack: [0x000000e205200000,0x000000e205300000], sp=0x000000e2052ff500, free space=1021k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [jvm.dll+0xb8c337] JvmtiBreakpoints::clearall_in_class_at_safepoint+0x97 (jvmtiImpl.cpp:273)
V [jvm.dll+0xb984e8] VM_RedefineClasses::redefine_single_class+0xc8 (jvmtiRedefineClasses.cpp:4198)
V [jvm.dll+0xb94b0b] VM_RedefineClasses::doit+0xeb (jvmtiRedefineClasses.cpp:269)
V [jvm.dll+0x10d5007] VM_Operation::evaluate+0xd7 (vmOperations.cpp:75)
V [jvm.dll+0x10d6d68] VMThread::evaluate_operation+0xb8 (vmThread.cpp:283)
V [jvm.dll+0x10d7557] VMThread::inner_execute+0x247 (vmThread.cpp:429)
V [jvm.dll+0x10d7b64] VMThread::run+0x114 (vmThread.cpp:176)
V [jvm.dll+0x10278d2] Thread::call_run+0x1b2 (thread.cpp:248)
V [jvm.dll+0xddec81] thread_native_entry+0xe1 (os_windows.cpp:562)
C [ucrtbase.dll+0x2268a] (no source info available)
C [KERNEL32.DLL+0x17ac4] (no source info available)
C [ntdll.dll+0x5a8c1] (no source info available)


siginfo: EXCEPTION_ACCESS_VIOLATION (0xc0000005), reading address 0x0000000000000008


The crash did not reproduce in the next Tier3 build-ID.