summaryrefslogtreecommitdiffstats
path: root/content/browser/child_process_launcher.cc
diff options
context:
space:
mode:
authorjam@chromium.org <jam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-07-30 21:00:43 +0000
committerjam@chromium.org <jam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2012-07-30 21:00:43 +0000
commit719a2059c71f84a883a73b4529c420761baf1a7c (patch)
tree82a8dfbe5128d84323e4105f4cc3e677c2d74181 /content/browser/child_process_launcher.cc
parentfc4f4dd485275e55b768c4deb9a253d17aeb7806 (diff)
downloadchromium_src-719a2059c71f84a883a73b4529c420761baf1a7c.zip
chromium_src-719a2059c71f84a883a73b4529c420761baf1a7c.tar.gz
chromium_src-719a2059c71f84a883a73b4529c420761baf1a7c.tar.bz2
On Posix, make all child processes quit when the browser dies, not just the renderers.
On bots, seeing that sometimes child processes are hanging around after the browser process is gone. This confuses the sharding scripts. BUG=90448 Review URL: https://chromiumcodereview.appspot.com/10834068 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149023 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/browser/child_process_launcher.cc')
-rw-r--r--content/browser/child_process_launcher.cc2
1 files changed, 1 insertions, 1 deletions
diff --git a/content/browser/child_process_launcher.cc b/content/browser/child_process_launcher.cc
index 2f8a272..f7cf772 100644
--- a/content/browser/child_process_launcher.cc
+++ b/content/browser/child_process_launcher.cc
@@ -58,7 +58,7 @@ class ChildProcessLauncher::Context
{
#if defined(OS_POSIX)
terminate_child_on_shutdown_ = !CommandLine::ForCurrentProcess()->
- HasSwitch(switches::kRendererCleanExit);
+ HasSwitch(switches::kChildCleanExit);
#else
terminate_child_on_shutdown_ = true;
#endif