[StorageMonitor] Move StorageMonitor ownership to BrowserProcessImpl

chrome/browser/extensions/api/media_galleries_private/media_galleries_private_apitest.cc

Index: chrome/browser/extensions/api/media_galleries_private/media_galleries_private_apitest.cc
diff --git a/chrome/browser/extensions/api/media_galleries_private/media_galleries_private_apitest.cc b/chrome/browser/extensions/api/media_galleries_private/media_galleries_private_apitest.cc
index 45737e56a2d84f6100fb3815ceeb8404ac0a9c5b..df662f08ec3e2878137ca4f9108e15927eb992e7 100644
--- a/chrome/browser/extensions/api/media_galleries_private/media_galleries_private_apitest.cc
+++ b/chrome/browser/extensions/api/media_galleries_private/media_galleries_private_apitest.cc
@@ -108,12 +108,8 @@ class MediaGalleriesPrivateApiTest : public ExtensionApiTest {
 };
 
 IN_PROC_BROWSER_TEST_F(MediaGalleriesPrivateApiTest, DeviceAttachDetachEvents) {
-  scoped_ptr<chrome::test::TestStorageMonitor> monitor(
-      chrome::test::TestStorageMonitor::CreateForBrowserTests());
-  monitor->Init();
-  monitor->MarkInitialized();
-
   // Setup.
+  chrome::test::TestStorageMonitor::SyncInitialize();

[vandebo (ex-Chrome), 2013/07/10 16:57:45]

Why is the test storage monitor setup different in eject_apitest and
private_apitest ?

[Greg Billock, 2013/07/10 21:11:16]

The eject one needs the mock object (we check for the eject call in the test).
This test can use the live object, but it needs to make sure the object is
initialized for the various force-fed registration calls it does.

   const extensions::Extension* extension =
       LoadExtension(test_data_dir_.AppendASCII(kTestExtensionPath));
   ASSERT_TRUE(extension);