-
Bug
-
Resolution: Fixed
-
P3
-
11, 17
-
b20
It's unlikely they will emit the same event as start/stop triggers event with "beginChunk", "endChunk" or "everyChunk", while periodic events have an interval, for example "1 s". Still, they might access the same data structure, for example Performance Counters on Windows.
This is very likely the solution for the "exitValue = -1073741819" error when using JFR on Windows, so we may want to consider a backport to JDK 11 and JDK 17.
- duplicates
-
JDK-8251849 jdk/jfr/startupargs/TestDumpOnExit.java failed with "exitValue = -1073741819"
-
- Closed
-
-
JDK-8273455 runtime/cds/appcds/dynamicArchive/JFRDynamicCDS.java failed with "exitValue = -1073741819"
-
- Closed
-
-
JDK-8214685 Passing illegal value for JFR startupargs causes SEGV or errors
-
- Closed
-
-
JDK-8253437 runtime/cds/appcds/jigsaw/modulepath/ModulePathAndCP_JFR.java failed with "exitValue = -1073741819"
-
- Closed
-
-
JDK-8259525 runtime/cds/appcds/CDSandJFR.java failed with "exitValue = -1073741819"
-
- Closed
-
-
JDK-8261603 vmTestbase/nsk/jvmti/AttachOnDemand/attach024/TestDescription.java failed with "non-zero code -1073741819"
-
- Closed
-
-
JDK-8277352 runtime/cds/appcds/customLoader/HelloCustom_JFR.java fails with exitValue = -1073741819
-
- Closed
-
- relates to
-
JDK-8258745 runtime/cds/appcds/CDSandJFR.java timed out
-
- Closed
-