Renderers should immediately exit on failure to send an IPC to the browser.

content/renderer/render_thread_impl.cc

Index: content/renderer/render_thread_impl.cc
diff --git a/content/renderer/render_thread_impl.cc b/content/renderer/render_thread_impl.cc
index d17d359334c3533da6d5266502ddf2ba036d1260..6b75695fe2640eaef392247c0c50af36419dd9f0 100644
--- a/content/renderer/render_thread_impl.cc
+++ b/content/renderer/render_thread_impl.cc
@@ -974,6 +974,15 @@ bool RenderThreadImpl::Send(IPC::Message* msg) {
 
   bool rv = ChildThreadImpl::Send(msg);
 
+  // In the fast shutdown path, the browser kills the IPC channel without
+  // informing the renderer. This means that any IPC message might fail. Either
+  // every sender of any IPC message needs to gracefully handle failures, or
+  // else the process needs to exit immediately. Since the renderer is no longer
+  // expected to have any user-visible effects, or make any persistent changes,
+  // exit immediately. https://crbug.com/615121.
+  if (!rv)
+    exit(EXIT_SUCCESS);

[jam, 2016/06/06 20:25:52]

seems like this should match exit(0) in SuicideOnChannelErrorFilter . I realize
both are 0, but we should be consistent in both of them.

Why isn't this in ChildThreadImpl::Send so that it's done for all child
processes instead of just renderers?

With this change,
https://codereview.chromium.org/2028833003/diff/60001/content/child/child_sha...
should that move to thread_safe_sender.cc's Send method instead?

+
   if (pumping_events) {
     WebView::didExitModalLoop();
     renderer_scheduler_->ResumeTimerQueue();