Comment #17 on issue 22703 by [email protected]: All subprocess
creation needs to go through zygote
http://code.google.com/p/chromium/issues/detail?id=22703
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=32457
------------------------------------------------------------------------
r32457 | [email protected] | 2009-11-18 17:02:06 -0800 (Wed, 18 Nov 2009) |
16 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/child_process_host.cc?r1=32457&r2=32456
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/chrome_constants.cc?r1=32457&r2=32456
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/test/chrome_process_util.cc?r1=32457&r2=32456
linux: use /proc/self/exe when exec'ing ourselves
We don't want to ever go out to disk when looking for data after
startup, since they can be changed by an update.
We *should* just be using the zygote, but the zygote is sandboxed-only
for now, and fixing that has a lengthy dependency graph. In the
interim, /proc/self/exe is the correct executable and exec'ing it should
work as long as the subprocess doesn't need any other files from the
Chrome directory.
BUG=22703
TEST=Start Chrome. Move away the entire Chrome directory; plugins
should still work.
Review URL: http://codereview.chromium.org/403018
------------------------------------------------------------------------
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
