[StorageMonitor] Move StorageMonitor ownership to BrowserProcessImpl

chrome/browser/chrome_browser_main_linux.cc

Index: chrome/browser/chrome_browser_main_linux.cc
diff --git a/chrome/browser/chrome_browser_main_linux.cc b/chrome/browser/chrome_browser_main_linux.cc
index dd83909c6e39137fd0e0c43b5a3a4636db11df7c..299154dee3104ea9041387873d9e6f8f734eee2c 100644
--- a/chrome/browser/chrome_browser_main_linux.cc
+++ b/chrome/browser/chrome_browser_main_linux.cc
@@ -118,11 +118,6 @@ void ChromeBrowserMainPartsLinux::PreProfileInit() {
   if (IsCrashReportingEnabled(local_state()))
     InitCrashReporter();
 
-#if !defined(OS_CHROMEOS)
-  const base::FilePath kDefaultMtabPath("/etc/mtab");
-  storage_monitor_.reset(new chrome::StorageMonitorLinux(kDefaultMtabPath));
-#endif
-
   ChromeBrowserMainPartsPosix::PreProfileInit();
 }
 
@@ -132,14 +127,3 @@ void ChromeBrowserMainPartsLinux::PostProfileInit() {
   g_browser_process->metrics_service()->RecordBreakpadRegistration(
       IsCrashReporterEnabled());
 }
-
-void ChromeBrowserMainPartsLinux::PostMainMessageLoopRun() {
-  ChromeBrowserMainPartsPosix::PostMainMessageLoopRun();
-
-#if !defined(OS_CHROMEOS)
-  // Delete it now. Otherwise the FILE thread would be gone when we try to
-  // release it in the dtor and Valgrind would report a leak on almost every
-  // single browser_test.
-  storage_monitor_.reset();
-#endif
-}