Don't close crashed tabs from extensions with background pages.

content/browser/tab_contents/render_view_host_manager.cc

Index: content/browser/tab_contents/render_view_host_manager.cc
diff --git a/content/browser/tab_contents/render_view_host_manager.cc b/content/browser/tab_contents/render_view_host_manager.cc
index 61b084b3f1f2e202b565eeb9e652a7dc0a8193a9..5480afc0f41fc6202cf068db592a6c673e77efec 100644
--- a/content/browser/tab_contents/render_view_host_manager.cc
+++ b/content/browser/tab_contents/render_view_host_manager.cc
@@ -96,6 +96,7 @@ RenderViewHost* RenderViewHostManager::Navigate(const NavigationEntry& entry) {
 
   // If the renderer crashed, then try to create a new one to satisfy this
   // navigation request.
+  // TODO(yoz): Should we try to reload extensions here instead??

[Matt Perry, 2011/11/10 22:07:59]

content/ shouldn't know about extensions. if we want to reload them at this
point, it would have to be in the delegate. just remove this TODO.

[Yoyo Zhou, 2011/11/10 23:26:30]

Yeah, this was from an earlier approach.

   if (!dest_render_view_host->IsRenderViewLive()) {
     if (!InitRenderView(dest_render_view_host, entry))
       return NULL;