$ JAVA_TOOL_OPTIONS="-XX:+UnlockDiagnosticVMOptions -XX:+UnlockExperimentalVMOptions -XX:+UseShenandoahGC -XX:StressSeed=2039903058" java -jar ./jcstress.jar -c 2 -t org.openjdk.jcstress.tests.copy.manual.objects.plain.StringTest
...
  VM output stream:
    #
    # A fatal error has been detected by the Java Runtime Environment:
    #
    # SIGSEGV (0xb) at pc=0x00007fa668d00ab0, pid=3266827, tid=3267280
    #
    # JRE version: OpenJDK Runtime Environment (17.0.14) (build 17.0.14-internal+0-adhoc.roland.jdk17u-dev)
    # Java VM: OpenJDK 64-Bit Server VM (17.0.14-internal+0-adhoc.roland.jdk17u-dev, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, shenandoah gc, linux-amd64)
    # Problematic frame:
    # J 385 c2 org.openjdk.jcstress.tests.copy.manual.objects.plain.StringTest_jcstress$JcstressThread_ResourceCheck_actor2.jcstress_check_actor2([Lorg/openjdk/jcstress/tests/copy/manual/objects/plain/StringTest;[Lorg/openjdk/jcstress/infra/results/L_Result;I)V (27 bytes) \
@ 0x00007fa668d00ab0 [0x00007fa668d009a0+0x0000000000000110]

We've only seen this with jdk 17 but I wrote a test case and could reproduce it with jdk 24.