ResourceScheduler should use renderer notifications instead of MRUCache to track renderers.

The MRUCache enforced a hard limit on the number of navigations we could track. If we have more than that, we stop scheduling and load everything at once. That will only make performance worse.

The renderer notifications should provide an accurate signal when tabs come and go. Instead of having a hard limit, we'll just follow the notifications.

BUG=None


Review URL: https://chromiumcodereview.appspot.com/12600018

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@188777 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 0 insertions, 17 deletions

diff --git a/content/browser/renderer_host/render_widget_helper.cc b/content/browser/renderer_host/render_widget_helper.cc
index 14204a7..1a3231d 100644
--- a/content/browser/renderer_host/render_widget_helper.cc
+++ b/content/browser/renderer_host/render_widget_helper.cc
@@ -127,17 +127,6 @@ RenderWidgetHelper* RenderWidgetHelper::FromProcessHostID(
   return (ci == g_widget_helpers.Get().end())? NULL : ci->second;
 }
 
-void RenderWidgetHelper::CancelResourceRequests(int render_widget_id) {
-  if (render_process_id_ == -1)
-    return;
-
-  BrowserThread::PostTask(
-      BrowserThread::IO, FROM_HERE,
-      base::Bind(&RenderWidgetHelper::OnCancelResourceRequests,
-                 this,
-                 render_widget_id));
-}
-
 void RenderWidgetHelper::SimulateSwapOutACK(
     const ViewMsg_SwapOut_Params& params) {
   BrowserThread::PostTask(
@@ -251,12 +240,6 @@ void RenderWidgetHelper::OnDispatchBackingStoreMsg(
     host->OnMessageReceived(proxy->message());
 }
 
-void RenderWidgetHelper::OnCancelResourceRequests(
-    int render_widget_id) {
-  resource_dispatcher_host_->CancelRequestsForRoute(
-      render_process_id_, render_widget_id);
-}
-
 void RenderWidgetHelper::OnSimulateSwapOutACK(
     const ViewMsg_SwapOut_Params& params) {
   resource_dispatcher_host_->OnSimulateSwapOutACK(params);