Android: remove ContentViewCore from the renderer crash codepath.

content/browser/child_process_launcher.cc

Index: content/browser/child_process_launcher.cc
diff --git a/content/browser/child_process_launcher.cc b/content/browser/child_process_launcher.cc
index 3b95c14dc65d2f9aa0d52a074ff2d079e3946664..8b3cbf8e388c0c73a0c575f43c217bba631745da 100644
--- a/content/browser/child_process_launcher.cc
+++ b/content/browser/child_process_launcher.cc
@@ -475,6 +475,10 @@ base::TerminationStatus ChildProcessLauncher::GetChildTerminationStatus(
     context_->termination_status_ =
         base::GetKnownDeadTerminationStatus(handle, &context_->exit_code_);
   } else

[jar (doing other things), 2013/11/06 19:27:26]

nit: This seems like a consistent style guide violation: Lacking curlies around
the else clause as well as the if clause.  I know it is harder to read in this
current format.

You can possibly make this more consistent (without messing with indents) using
a pattern such as:

if () {
} else if () {
...
} else if () {
etc.

[ppi, 2013/11/06 20:14:06]

I'm not sure if I see how this could work. We can't start each platform-specific
bit with "} else if (...) {", because it will be only one (platform-specific
#elif chunk) that will be compiled each time and it needs to start with "if ()
{".

I agree the current way looks confusing. I added braces to "else" clauses in
patch set 5, but I am not sure if it is easier to read that way.

+#elif defined(OS_ANDROID)
+  if (IsChildProcessOomProtected(handle)) {
+      context_->termination_status_ = base::TERMINATION_STATUS_OOM_PROTECTED;
+  } else
 #endif
   {
     context_->termination_status_ =