ADDITIONAL SYSTEM INFORMATION :
Windows 10. Java 19 EA Build 33.

A DESCRIPTION OF THE PROBLEM :
We started using Java 19 in our CI and observed 5 crashes during System.exit on Windows. The same application runs without problems with Java 18.

hs_err_pid file contains:

Current thread (0x000001cdfca2a5e0): JavaThread "main" [_thread_in_vm, id=12860, stack(0x00000052d1a00000,0x00000052d1b00000)] _threads_hazard_ptr=0x000001cdfca1e2f0Stack: [0x00000052d1a00000,0x00000052d1b00000], sp=0x00000052d1afed60, free space=1019k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [jvm.dll+0x5832a0]
V [jvm.dll+0x582a20]
V [jvm.dll+0x58358c]
V [jvm.dll+0x577e52]
V [jvm.dll+0x5346ee]
C [jdwp.dll+0x146d7]Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j java.lang.Shutdown.halt0(I)V+0 java.base@19-ea
j java.lang.Shutdown.halt(I)V+7 java.base@19-ea
j java.lang.Shutdown.exit(I)V+42 java.base@19-ea
j java.lang.Runtime.exit(I)V+23 java.base@19-ea
j java.lang.System.exit(I)V+4 java.base@19-ea
j XY.main([Ljava/lang/String;)V+14
v ~StubRoutines::call_stub 0x000001cd8f29100esiginfo: EXCEPTION_ACCESS_VIOLATION (0xc0000005), writing address 0x000001cd9efa2bec

If necessary, I can upload the hs_err_pid.log and hs_err_pid.mdmp somewhere.

Please note that application was started with a JVMTI agent.

Unfortunately I was unable to resolve the native stack trace or do any debugging myself. Are debug symbols (PDBs) available publicly?

REGRESSION : Last worked in version 18.0.2

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
I am unable to provide a reproducer at the moment.


FREQUENCY : occasionally