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

content/browser/loader/render_view_host_tracker.h

Index: content/browser/loader/render_view_host_tracker.h
diff --git a/content/browser/loader/render_view_host_tracker.h b/content/browser/loader/render_view_host_tracker.h
new file mode 100644
index 0000000000000000000000000000000000000000..71b84cd51510c9e966ed6a19eaa4ccead79398af
--- /dev/null
+++ b/content/browser/loader/render_view_host_tracker.h
@@ -0,0 +1,34 @@
+// Copyright (c) 2013 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef CONTENT_BROWSER_LOADER_RENDER_VIEW_HOST_TRACKER_H_
+#define CONTENT_BROWSER_LOADER_RENDER_VIEW_HOST_TRACKER_H_
+
+#include "content/public/browser/notification_observer.h"
+#include "content/public/browser/notification_registrar.h"
+
+namespace content {
+
+// The ResourceDispatcherHost needs to know when renderers are created and
+// destroyed. That happens on the UI thread, but the ResourceDispatcherHost
+// operates on the IO thread. RenderViewHostTracker listens for renderer
+// notifications on the UI thread, then bounces them over to the IO thread so
+// the ResourceDispatcherHost can be notified.
+class CONTENT_EXPORT RenderViewHostTracker : public NotificationObserver {
+ public:
+  RenderViewHostTracker();
+  virtual ~RenderViewHostTracker();
+
+ private:
+  // NotificationObserver interface:
+  virtual void Observe(int type,
+                       const NotificationSource& source,
+                       const NotificationDetails& details) OVERRIDE;
+
+  content::NotificationRegistrar registrar_;
+};
+
+}  // namespace content
+
+#endif  // CONTENT_BROWSER_LOADER_RENDER_VIEW_HOST_TRACKER_H_