This is likely a product bug (not a test bug), for the initial evaluation.
Frequency: fails about once a week in CI
Platform: only seen on Windows so far
Update: added a sighting on Linux.


The test uses Unsafe to write 0 into 0 address, thus causing Access Vialation, and the JFR recording dump.
Test verifies the recording, specifically the ShutdownEvent. Looks like the stack trace is incorrect, thus test asserts.


java.lang.RuntimeException: assertFalse: expected false, was true
at jdk.test.lib.Asserts.fail(Asserts.java:594)
at jdk.test.lib.Asserts.assertFalse(Asserts.java:461)
at jdk.test.lib.Asserts.assertFalse(Asserts.java:447)
at jdk.jfr.event.runtime.TestShutdownEvent.validateStackTrace(TestShutdownEvent.java:128)
at jdk.jfr.event.runtime.TestShutdownEvent$TestVMCrash.verifyEvents(TestShutdownEvent.java:172)
at jdk.jfr.event.runtime.TestShutdownEvent.runSubtest(TestShutdownEvent.java:105)
at jdk.jfr.event.runtime.TestShutdownEvent.main(TestShutdownEvent.java:72)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:567)
at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:127)
at java.base/java.lang.Thread.run(Thread.java:835)