DevTools: Fixed handling of unexpected renderer termination

chrome/browser/devtools/devtools_window.cc

Index: chrome/browser/devtools/devtools_window.cc
diff --git a/chrome/browser/devtools/devtools_window.cc b/chrome/browser/devtools/devtools_window.cc
index da8615c14703f1527e6d3b42a82c26128f7d110c..77fa23bd5349bbcb5f6adf1e56fafb106c74e2c3 100644
--- a/chrome/browser/devtools/devtools_window.cc
+++ b/chrome/browser/devtools/devtools_window.cc
@@ -1020,8 +1020,14 @@ InfoBarService* DevToolsWindow::GetInfoBarService() {
 }
 
 void DevToolsWindow::RenderProcessGone() {
+  // Do this first so that when GetDockedInstanceForInspectedTab is called
+  // from CloseContents it won't return this instance
+  // see crbug.com/372504
+  content::DevToolsManager::GetInstance()->ClientHostClosing(
+      bindings_->frontend_host());
   // Docked DevToolsWindow owns its web_contents_ and must delete it.
   // Undocked web_contents_ are owned and handled by browser.
+  // see crbug.com/369932
   if (is_docked_)
     CloseContents(web_contents_);

[pfeldman, 2014/05/15 14:23:51]

Lets put it into CloseContents.

 }