Don't fork Zygote as a background process
On Linux, with the setuid sandbox, the Zygote would become a background
process of sort because the setuid sandbox would exit.
The problem is that the Chrome process tree would be broken because the
Zygote would be reparented to init.
In turn, this could create issues with the browser not being able to ptrace()
the Zygote if certain kernel restrictions are in place (e.g. Yama).
BUG=125225
TEST=
NOTRY=true
Review URL: https://chromiumcodereview.appspot.com/10447135
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@140104 0039d316-1c4b-4281-b951-d872f2087c98
2 files changed