The following test failed in the JDK14 CI:

jdk/jfr/jvm/TestDumpOnCrash.java

Here's a snippet from the log file:

----------System.out:(31/2424)*----------
Test case for crasher jdk.jfr.jvm.TestDumpOnCrash$CrasherIllegalAccess
Command line: [c:\\ade\\mesos\\work_dir\\jib-master\\install\\jdk-14+20-840\\windows-x64-debug.jdk\\jdk-14\\fastdebug\\bin\\java.exe -cp T:\\testoutput\\test-support\\jtreg_open_test_jdk_jdk_svc\\classes\\0\\jdk\\jfr\\jvm\\TestDumpOnCrash.d;C:\\ade\\mesos\\work_dir\\jib-master\\install\\jdk-14+20-840\\src.full\\open\\test\\jdk\\jdk\\jfr\\jvm;T:\\testoutput\\test-support\\jtreg_open_test_jdk_jdk_svc\\classes\\0\\test\\lib;C:\\ade\\mesos\\work_dir\\jib-master\\install\\jdk-14+20-840\\src.full\\open\\test\\lib;C:\\ade\\mesos\\work_dir\\jib-master\\install\\java\\re\\jtreg\\4.2\\promoted\\all\\b14\\bundles\\jtreg_bin-4.2.zip\\jtreg\\lib\\javatest.jar;C:\\ade\\mesos\\work_dir\\jib-master\\install\\java\\re\\jtreg\\4.2\\promoted\\all\\b14\\bundles\\jtreg_bin-4.2.zip\\jtreg\\lib\\jtreg.jar -Xmx512m -XX:MaxRAMPercentage=3 -ea -esa -XX:NativeMemoryTracking=detail -Xmx64m -XX:-CreateCoredumpOnCrash --add-exports=java.base/jdk.internal.misc=ALL-UNNAMED -XX:StartFlightRecording=dumponexit=true,disk=true jdk.jfr.jvm.TestDumpOnCrash$CrasherIllegalAccess ]
[2019-10-18T09:09:05.867916500Z] Gathering output for process 37416
========== Crasher process output:
Started recording 1. No limit specified, using maxsize=250MB as default.

Use jcmd 37416 JFR.dump name=1 filename=FILEPATH to copy recording data to file.

[error occurred during error reporting ((null)), id 0xe0000000, Internal Error (t:/workspace/open/src/hotspot/share/jfr/recorder/storage/jfrBuffer.cpp:58)]

#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffa3f041931, pid=37416, tid=27960
#
# JRE version: Java(TM) SE Runtime Environment (14.0+20) (fastdebug build 14-ea+20-840)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (fastdebug 14-ea+20-840, mixed mode, sharing, tiered, compressed oops, g1 gc, windows-amd64)
# Problematic frame:
# V [jvm.dll+0xca1931][thread 43096 also had an error]
  Unsafe_PutInt+0x161
#
# CreateCoredumpOnCrash turned off, no core file dumped
#
# An error report file with more information is saved as:
# T:\\testoutput\\test-support\\jtreg_open_test_jdk_jdk_svc\\scratch\\7\\hs_err_pid37416.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
#

==================================
----------System.err:(16/1406)*----------
java.lang.RuntimeException: No emergency jfr recording file T:\\testoutput\\test-support\\jtreg_open_test_jdk_jdk_svc\\scratch\\7\\hs_err_pid37416.jfr exists: expected true, was false
at jdk.test.lib.Asserts.fail(Asserts.java:594)
at jdk.test.lib.Asserts.assertTrue(Asserts.java:486)
at jdk.jfr.jvm.TestDumpOnCrash.verify(TestDumpOnCrash.java:115)
at jdk.jfr.jvm.TestDumpOnCrash.main(TestDumpOnCrash.java:80)
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:564)
at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:127)
at java.base/java.lang.Thread.run(Thread.java:830)

JavaTest Message: Test threw exception: java.lang.RuntimeException: No emergency jfr recording file T:\\testoutput\\test-support\\jtreg_open_test_jdk_jdk_svc\\scratch\\7\\hs_err_pid37416.jfr exists: expected true, was false
JavaTest Message: shutting down test

STATUS:Failed.`main' threw exception: java.lang.RuntimeException: No emergency jfr recording file T:\\testoutput\\test-support\\jtreg_open_test_jdk_jdk_svc\\scratch\\7\\hs_err_pid37416.jfr exists: expected true, was false
----------rerun:(43/4976)*----------


Another bug mentions this test:

    JDK-8219680 JFR fails to generate emergency recording upon SIG FPE

but this failure mode is not SIGFPE so I filed a new bug.