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

content/browser/renderer_host/render_process_host_impl.cc

Index: content/browser/renderer_host/render_process_host_impl.cc
diff --git a/content/browser/renderer_host/render_process_host_impl.cc b/content/browser/renderer_host/render_process_host_impl.cc
index dcc1838f2fd2a25e5487bda013706d3a0f543ff9..5555dd9e55d56cce2248c104bb26b4508fe40136 100644
--- a/content/browser/renderer_host/render_process_host_impl.cc
+++ b/content/browser/renderer_host/render_process_host_impl.cc
@@ -615,10 +615,6 @@ int RenderProcessHostImpl::GetNextRoutingID() {
   return widget_helper_->GetNextRoutingID();
 }
 
-void RenderProcessHostImpl::CancelResourceRequests(int render_widget_id) {
-  widget_helper_->CancelResourceRequests(render_widget_id);
-}
-
 void RenderProcessHostImpl::SimulateSwapOutACK(
     const ViewMsg_SwapOut_Params& params) {
   widget_helper_->SimulateSwapOutACK(params);
@@ -1150,9 +1146,6 @@ void RenderProcessHostImpl::Release(int routing_id) {
   DCHECK(render_widget_hosts_.Lookup(routing_id) != NULL);
   render_widget_hosts_.Remove(routing_id);
 
-  // Make sure that all associated resource requests are stopped.
-  CancelResourceRequests(routing_id);
-
 #if defined(OS_WIN)
   // Dump the handle table if handle auditing is enabled.
   const CommandLine& browser_command_line =