-
Bug
-
Resolution: Fixed
-
P4
-
22, 23
-
b07
-
generic
-
generic
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8324414 | 22.0.1 | Daniel Daugherty | P4 | Resolved | Fixed | b02 |
JDK-8324150 | 22 | Daniel Daugherty | P4 | Resolved | Fixed | b33 |
java/foreign/critical/TestCriticalUpcall.java causes a VM crash
and checks crash output for "wrong thread state for upcall".
However, it also generates a core file that is not needed for
the test to pass.
For my stress test runs this test generates one core in release,
fastdebug and slowdebug runs and I do 3 runs per stress run.
That's 9 cores and on my M1 MacMini they are 4GB each so
that's 36GB in core files that I don't need.
If I don't remember to run "sysctl kern.corefile=../core.%P" every
time I reboot the M1 MacMini they start accumulating in /cores...
and checks crash output for "wrong thread state for upcall".
However, it also generates a core file that is not needed for
the test to pass.
For my stress test runs this test generates one core in release,
fastdebug and slowdebug runs and I do 3 runs per stress run.
That's 9 cores and on my M1 MacMini they are 4GB each so
that's 36GB in core files that I don't need.
If I don't remember to run "sysctl kern.corefile=../core.%P" every
time I reboot the M1 MacMini they start accumulating in /cores...
- backported by
-
JDK-8324150 java/foreign/critical/TestCriticalUpcall.java does not need a core file
-
- Resolved
-
-
JDK-8324414 java/foreign/critical/TestCriticalUpcall.java does not need a core file
-
- Resolved
-
- links to
-
Commit openjdk/jdk22/b1788944
-
Commit openjdk/jdk/a22ae909
-
Review openjdk/jdk22/90
-
Review openjdk/jdk/17476
(1 links to)