Create base::win::MemoryPressureMonitor class.

content/browser/browser_main_loop.h

Index: content/browser/browser_main_loop.h
diff --git a/content/browser/browser_main_loop.h b/content/browser/browser_main_loop.h
index 0a9e387eef262c50034e9ef9233651f5be02b106..b3eeab2e160723b45c96a2c20172bbbe18e0c7b3 100644
--- a/content/browser/browser_main_loop.h
+++ b/content/browser/browser_main_loop.h
@@ -24,6 +24,8 @@ class SystemMonitor;
 class MemoryPressureMonitorChromeOS;
 #elif defined(OS_MACOSX)
 class MemoryPressureMonitorMac;
+#elif defined(OS_WIN)
+class MemoryPressureMonitorWin;
 #endif
 namespace trace_event {
 class TraceMemoryController;
@@ -184,6 +186,8 @@ class CONTENT_EXPORT BrowserMainLoop {
   scoped_ptr<base::MemoryPressureMonitorChromeOS> memory_pressure_monitor_;
 #elif defined(OS_MACOSX) && !defined(OS_IOS)
   scoped_ptr<base::MemoryPressureMonitorMac> memory_pressure_monitor_;
+#elif defined(OS_WIN)
+  scoped_ptr<base::MemoryPressureMonitorWin> memory_pressure_monitor_;

[grt (UTC plus 2), 2015/05/05 15:34:00]

can some/all of these be scoped_ptr<base::MemoryPressureMonitor>? if not, why
not? that's the whole point of implementing this thing in terms of an abstract
base class, no?

[chrisha, 2015/05/05 19:46:13]

Yeah, the Windows and Mac ones can be folded. The ChromeOS one has some extra
member functions that aren't in the base class.

 #endif
   // The startup task runner is created by CreateStartupTasks()
   scoped_ptr<StartupTaskRunner> startup_task_runner_;