Very strange failure mode, seen once in our CI and once in a personal job in our CI system on macOS:
command: main -Djdk.lang.Process.launchMechanism=FORK -Xrs UnblockSignals
reason: User specified action: run main/othervm -Djdk.lang.Process.launchMechanism=FORK -Xrs UnblockSignals
started: Mon Aug 25 07:38:12 GMT 2025
Mode: othervm [/othervm specified]
Process id: 88824
finished: Mon Aug 25 07:40:25 GMT 2025
elapsed time (seconds): 133.525
----------configuration:(0/0)----------
----------System.out:(32/56)----------
[Too many errors, abort]
----------System.err:(1/96)----------
java(88827) MallocStackLogging: can't turn off malloc stack logging because it was not enabled.
All the whitespace is as per the log - which is really weird. No idea where the "too many errors" is coming from - nor the MallocStackLogging message!
Most recent change to Process code wasJDK-8364611
command: main -Djdk.lang.Process.launchMechanism=FORK -Xrs UnblockSignals
reason: User specified action: run main/othervm -Djdk.lang.Process.launchMechanism=FORK -Xrs UnblockSignals
started: Mon Aug 25 07:38:12 GMT 2025
Mode: othervm [/othervm specified]
Process id: 88824
finished: Mon Aug 25 07:40:25 GMT 2025
elapsed time (seconds): 133.525
----------configuration:(0/0)----------
----------System.out:(32/56)----------
[Too many errors, abort]
----------System.err:(1/96)----------
java(88827) MallocStackLogging: can't turn off malloc stack logging because it was not enabled.
All the whitespace is as per the log - which is really weird. No idea where the "too many errors" is coming from - nor the MallocStackLogging message!
Most recent change to Process code was
- relates to
-
JDK-8364611 (process) Child process SIGPIPE signal disposition should be default
-
- Resolved
-