Runtime.exec : vfork() concerns and a fix proposal
martinrb at google.com
Wed Sep 12 16:01:33 UTC 2018
On Wed, Sep 12, 2018 at 8:16 AM, David Lloyd <david.lloyd at redhat.com> wrote:
> Seems worthwhile though, given vfork's now-10-year-old obsolescence.
> It looks like Linux is the only platform still using vfork for
> ProcessImpl in OpenJDK.
I'm fine with switching to posix_spawn on Linux as long as we don't
reintroduce the memory overcommit problem, which would be a
deal-breaker. But glibc posix_spawn will use either vfork or clone
with CLONE_VFORK, so we should be OK.
More information about the core-libs-dev