RFR 8027434: "-XX:OnOutOfMemoryError" uses fork instead of vfork
fw at deneb.enyo.de
Thu Sep 27 19:08:05 UTC 2018
* David Holmes:
> I think you may be missing my point. We take a signal that will
> terminate the VM, and from the signal handler context start the error
> reporting and as part of that try to fork_and_exec the onError command
> requested by the user. My recollection from reading all this stuff is
> that vfork may not be safe to call from a signal context.
On GNU/Linux, fork is not safe, either:
This is particularly visible if you've got a SIGSEGV handler that is
called from malloc after heap corruption. Then fork will most likely
hang due to a self-deadlock.
vfork might actually be safer in this context because it does not run
any fork handlers, but only if you take the required measures to use
it safely. On the other hand, the rest of the process will keep
running, so you don't get the snapshot functionality that comes from
In my opinion (reflected in the cited article), crash handlers should
live outside the process, at least on Linux.
> That's why I suggested we only switch this for the OnOutOfMemoryError
> case as it's not (normally?) executed from a signal context.
If it's a native OnOutOfMemoryError (is there such a thing?), then
both vfork and fork are likely to fail themselves (but fork is more
likely to do so).
More information about the hotspot-runtime-dev