Remove debugging for crbug.com/1006814

The crash has not occurred since https://crrev.com/c/2186901,
submitted on May 12.

Some of the dchecks etc remain and some todos updated to point to the
main RenderDocument bug.

Bug: 1006814
Change-Id: Id078eed913addbc4444050dff5f76e357e8a3e40
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2214766
Commit-Queue: Fergal Daly <[email protected]>
Reviewed-by: Alex Moshchuk <[email protected]>
Cr-Commit-Position: refs/heads/master@{#774008}
diff --git a/content/browser/web_contents/web_contents_impl.cc b/content/browser/web_contents/web_contents_impl.cc
index d2b8edd0..28734c1 100644
--- a/content/browser/web_contents/web_contents_impl.cc
+++ b/content/browser/web_contents/web_contents_impl.cc
@@ -2159,8 +2159,7 @@
   // corresponding RenderView and main RenderFrame have already been created.
   // Ensure observers are notified about this.
   if (params.renderer_initiated_creation) {
-    GetRenderViewHost()->GetWidget()->SetRendererInitialized(
-        true, RenderWidgetHostImpl::RendererInitializer::kWebContentsInit);
+    GetRenderViewHost()->GetWidget()->set_renderer_initialized(true);
     GetRenderViewHost()->DispatchRenderViewCreated();
     GetRenderManager()->current_frame_host()->SetRenderFrameCreated(true);
   }