Remove old diagnostic crash reports.

content/browser/renderer_host/render_view_host_impl.cc

Index: content/browser/renderer_host/render_view_host_impl.cc
diff --git a/content/browser/renderer_host/render_view_host_impl.cc b/content/browser/renderer_host/render_view_host_impl.cc
index 0e80165d72ae40dd26db592606a2288f3ba6bbb1..c1be50590329cd60b632b58982b3b7eebb911d1b 100644
--- a/content/browser/renderer_host/render_view_host_impl.cc
+++ b/content/browser/renderer_host/render_view_host_impl.cc
@@ -276,14 +276,6 @@ bool RenderViewHostImpl::CreateRenderView(
   CHECK(main_frame_routing_id_ != MSG_ROUTING_NONE ||
         proxy_route_id != MSG_ROUTING_NONE);
 
-  // We should not set both main_frame_routing_id_ and proxy_route_id.  Log
-  // cases that this happens (without crashing) to track down
-  // https://crbug.com/575245.
-  // TODO(creis): Remove this once we've found the cause.
-  if (main_frame_routing_id_ != MSG_ROUTING_NONE &&
-      proxy_route_id != MSG_ROUTING_NONE)

[alexmos, 2016/12/13 20:28:55]

Would there be value in keeping this as a DCHECK?  And/or a CHECK, perhaps in
RVI::Initialize?  AFAICT, we happily create both a main RF and a proxy if this
ever happens, and I don't think any good can come out of that. :)

[Charlie Reis, 2017/05/09 16:42:26]

Sure, we can keep it as a DCHECK here.

-    base::debug::DumpWithoutCrashing();
-
   GetWidget()->set_renderer_initialized(true);
 
   mojom::CreateViewParamsPtr params = mojom::CreateViewParams::New();