[StorageMonitor] Move StorageMonitor ownership to BrowserProcessImpl

chrome/browser/storage_monitor/test_storage_monitor.h

Index: chrome/browser/storage_monitor/test_storage_monitor.h
diff --git a/chrome/browser/storage_monitor/test_storage_monitor.h b/chrome/browser/storage_monitor/test_storage_monitor.h
index 6408e6657c9423f2dcb42d1c6a0321d79806ad12..b7d483502e042e91806863a12eeeb1b51095d213 100644
--- a/chrome/browser/storage_monitor/test_storage_monitor.h
+++ b/chrome/browser/storage_monitor/test_storage_monitor.h
@@ -21,10 +21,16 @@ class TestStorageMonitor : public chrome::StorageMonitor {
 
   void MarkInitialized();
 
-  // Will create a new testing implementation for browser tests,
-  // taking care to deal with the existing singleton correctly.
+  // Create an initialize a new TestStorageMonitor, and install it
+  // in the browser process.
+  static TestStorageMonitor* Create();

[Lei Zhang, 2013/07/02 23:16:57]

I have trouble telling the difference between Create() and
CreateForBrowserTests(). They seem to do the same thing in slightly different
ways.

[Greg Billock, 2013/07/03 17:49:17]

Yes. Create() puts it in the TestingBrowserProcess, and CreateForBrowserTests
puts it into BrowserProcessImpl. I'll clarify this.

   static TestStorageMonitor* CreateForBrowserTests();
 
+  static void RemoveSingleton();
+
+  // Synchronously initialize the current storage monitor.
+  static void SyncInitialize();
+
   virtual bool GetStorageInfoForPath(
       const base::FilePath& path,
       StorageInfo* device_info) const OVERRIDE;