Prevent unauthorized commits of the Chrome Web Store URL.

content/browser/renderer_host/render_process_host_impl.cc

Index: content/browser/renderer_host/render_process_host_impl.cc
diff --git a/content/browser/renderer_host/render_process_host_impl.cc b/content/browser/renderer_host/render_process_host_impl.cc
index 2e7bba8213b63d973faae74ba03d1c3731754d5a..3a4e4ea6377ea13cedbc306396c6d24c8c744f07 100644
--- a/content/browser/renderer_host/render_process_host_impl.cc
+++ b/content/browser/renderer_host/render_process_host_impl.cc
@@ -721,7 +721,8 @@ void RenderProcessHostImpl::ReceivedBadMessage() {
     // crash.
     CHECK(false);
   }
-  NOTREACHED();
+  // We kill the renderer but don't include a NOTREACHED, because it is possible

[nasko, 2013/05/13 18:14:27]

nit: "it is possible" doesn't seem as strong messaging to me. Chrome better be
able to survive a malformed messages/rogue renderers.

[Charlie Reis, 2013/05/13 20:10:51]

We can't always survive: renderers can kill the browser process using resource
exhaustion, etc.  But you're right that we should try to survive.  Comment
updated.

+  // for the browser to survive when it gets illegal messages from the renderer.
   base::KillProcess(GetHandle(), RESULT_CODE_KILLED_BAD_MESSAGE,
                     false);
 }