Move ClosePage() from RenderViewHost to WebContents.

extensions/browser/process_manager.cc

Index: extensions/browser/process_manager.cc
diff --git a/extensions/browser/process_manager.cc b/extensions/browser/process_manager.cc
index 47f7b191e004da8dccf2a6179c9a17a73471752f..d1908d2cd79155947f6e0cf7cffabe739a67f223 100644
--- a/extensions/browser/process_manager.cc
+++ b/extensions/browser/process_manager.cc
@@ -805,8 +805,8 @@ void ProcessManager::CloseLazyBackgroundPageNow(const std::string& extension_id,
       }
     }
     for (content::RenderFrameHost* frame : frames_to_close) {
-      frame->GetRenderViewHost()->ClosePage();
-      // RenderViewHost::ClosePage() may result in calling
+      content::WebContents::FromRenderFrameHost(frame)->ClosePage();

[Charlie Reis, 2015/04/29 17:31:18]

The interstitial CL reminded me that this might return null.  Should we add a
null check?

[nasko, 2015/04/29 21:15:33]

Should we ever be getting a background page RFH that has interstitial page? I
don't think it is possible, so I'm inclined to leave this as is and monitor if
we get any crashes.

[Charlie Reis, 2015/04/29 22:21:48]

I hadn't thought of a specific case it could happen; it just seemed unclear if
that was an invariant you intended to enforce.  Feel free to leave and monitor
for crashes.

+      // WebContents::ClosePage() may result in calling
       // UnregisterRenderViewHost() asynchronously and may cause race conditions
       // when the background page is reloaded.
       // To avoid this, unregister the view now.