DevTools: don't show the unresponsive dialog for inspected tabs

content/browser/tab_contents/tab_contents.cc

Index: content/browser/tab_contents/tab_contents.cc
diff --git a/content/browser/tab_contents/tab_contents.cc b/content/browser/tab_contents/tab_contents.cc
index 21973397e6e9c311d0766b4829fc256a0a3c4b52..bc75a0b9f9cdcc4eb06532cf7e1f1c9106742d2b 100644
--- a/content/browser/tab_contents/tab_contents.cc
+++ b/content/browser/tab_contents/tab_contents.cc
@@ -1758,6 +1758,13 @@ void TabContents::RendererUnresponsive(RenderViewHost* rvh,
   if (rvh != render_view_host())
     return;
 
+  // Ignore renderer unresponsive event if debugger is attached to the tab
+  // since the event may be a result of the renderer sitting on a breakpoint.
+  // See http://crbug.com/65458
+  DevToolsManager* devtools_manager = DevToolsManager::GetInstance();
+  if (devtools_manager && devtools_manager->IsBeingDebugged(rvh))

[pfeldman1, 2011/08/03 16:28:50]

What if the page has in fact hit the infinite loop? Consider the following
scenario:

- developer observes watchdog
- he wants to investigate the cause
- he opens devtools and watchdog vanishes

I think we should send the heart beat from the renderer (once a second or so)
while paused. That way we will reset the watchdog in browser and it will never
hit the limit while paused.

+    return;
+
   if (is_during_unload) {
     // Hang occurred while firing the beforeunload/unload handler.
     // Pretend the handler fired so tab closing continues as if it had.