Reported at https://mail.openjdk.org/pipermail/leyden-dev/2024-July/000768.html

With the patch described in JDK-8335735, we get a different crash with jruby:

When I try to use the previously trained CDS dump (via 100.times { org.jruby.Ruby.newInstance }) with a command line that forces C1 (--dev flag passes -XX:TieredStopAtLevel=1) I get a different crash: https://gist.github.com/headius/d3138efa52eed9c678414c8cfe08af27

=====================
A easier reproducer (with 2024/07/09 Leyden premain repo)

$ rm -f HelloWorld.cds

# create archive
$ java -XX:CacheDataStore=javac.cds -cp HelloWorld.jar HelloWorld.jar
HelloWorld

# run with archive = OK
$ java -XX:CacheDataStore=javac.cds -cp HelloWorld.jar HelloWorld.jar
HelloWorld

# run with archive but force C1 = crash
$ java -XX:CacheDataStore=javac.cds -cp HelloWorld.jar HelloWorld.jar -XX:TieredStopAtLevel=1 HelloWorld
# A fatal error has been detected by the Java Runtime Environment:
#
# Internal Error (/jdk3/le3/open/src/hotspot/share/compiler/compileBroker.cpp:1587), pid=456573, tid=456574
# assert(comp != nullptr) failed: Ensure we have a compiler
#
# JRE version: Java(TM) SE Runtime Environment (24.0) (fastdebug build 24-internal-adhoc.iklam.le3)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (fastdebug 24-internal-adhoc.iklam.le3, mixed mode, emulated-client, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# V [libjvm.so+0xa3fe09] CompileBroker::compile_method(methodHandle const&, int, int, methodHandle const&, int, bool, CompileTask::CompileReason, JavaThread*)+0x179
#
# No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /jdk3/le3/open/src/hotspot/hs_err_pid456573.log
#
# If you would like to submit a bug report, please visit:
# https://bugreport.java.com/bugreport/crash.jsp
#