chrome: respect --child-clean-exit.

content/app/content_main_runner.cc

Index: content/app/content_main_runner.cc
diff --git a/content/app/content_main_runner.cc b/content/app/content_main_runner.cc
index 5bbdb9b35d81c001374fa3b495ae5430bc16224a..460e6ed61770a33bdb182910643c00947afcf72a 100644
--- a/content/app/content_main_runner.cc
+++ b/content/app/content_main_runner.cc
@@ -5,6 +5,8 @@
 #include "content/public/app/content_main_runner.h"
 
 #include <stdlib.h>
+#include <sys/types.h>
+#include <sys/wait.h>
 
 #include "base/allocator/allocator_extension.h"
 #include "base/at_exit.h"
@@ -786,6 +788,13 @@ class ContentMainRunnerImpl : public ContentMainRunner {
 
     exit_manager_.reset(NULL);
 
+    // Wait for children to exit if --child-clean-exit is passed.
+    if (CommandLine::ForCurrentProcess()->
+        HasSwitch(switches::kChildCleanExit)) {
+      while (wait(NULL) != -1);

[Markus (顧孟勤), 2013/07/22 22:50:13]

Minor nit-pick (feel free to avoid).

This looks very much like an anti-pattern:
http://c-faq.com/strangeprob/emptyloop.html

I'd prefer if you were more verbose, just to make sure nobody "fixes" this code
at some point in the future.

How about:

for (;;) {
  if (wait(NULL) < 0 && errno == ECHILD) {
    break;
  }
}

This also has the advantage of looping on EINTR.

Otherwise, at least consider adding HANDLE_EINTR(wait(NULL));

[asharif1, 2013/07/22 23:43:54]

I can easily make this change, but please comment on the other issue I'm seeing,
which is described in a message along with my replies to your comments.

[asharif1, 2013/07/24 15:17:23]

Done.

+    }
+
+
     delegate_ = NULL;
     is_shutdown_ = true;
   }