Consider deprecating this in JDK 21
Turning UseOSErrorReporting halts the VM process during crash report, eventually times out with message: "[ timer expired, abort... ]" on macOS and Linux. It doesn't do that on Windows, but does it actually do anything useful?
I tried it on Windows 10 and personally I did not spot any difference with the flag ON/OFF from the point of the user/developer - in particular I see no system crash reports.
On Windows, similar to Mac and Linux we seem stuck in infinite loop and the only reason the process does not time out is that after about 250 loops it gets stack space exception.
Might need a similar fox to that for POSIX (i.e.JDK-8250637)
Turning UseOSErrorReporting halts the VM process during crash report, eventually times out with message: "[ timer expired, abort... ]" on macOS and Linux. It doesn't do that on Windows, but does it actually do anything useful?
I tried it on Windows 10 and personally I did not spot any difference with the flag ON/OFF from the point of the user/developer - in particular I see no system crash reports.
On Windows, similar to Mac and Linux we seem stuck in infinite loop and the only reason the process does not time out is that after about 250 loops it gets stack space exception.
Might need a similar fox to that for POSIX (i.e.
- clones
-
JDK-8250637 UseOSErrorReporting times out (on Mac and Linux)
- Resolved
- relates to
-
JDK-8294031 GCC 12 fails to compile AArch64 due to -Wstringop-overflow
- Closed
-
JDK-4997835 RFE: crash dump will only be created when running w/ -XX:+ShowMessageBoxOnError
- Closed
-
JDK-8237727 Mac: after we handle a crash, Apple's crash reporter is left with incorrect state
- Closed