[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 3a3ea520aa933af80820ae281efd38bdd00b2931..de68d1d440293f171ef3b67941d75c4cfb5de04f 100644
--- a/chrome/browser/chrome_browser_main_linux.cc
+++ b/chrome/browser/chrome_browser_main_linux.cc
@@ -5,7 +5,6 @@
 #include "chrome/browser/chrome_browser_main_linux.h"
 
 #if !defined(OS_CHROMEOS)
-#include "chrome/browser/storage_monitor/storage_monitor_linux.h"
 #include "content/public/browser/browser_thread.h"
 #endif
 
@@ -125,21 +124,5 @@ void ChromeBrowserMainPartsLinux::PreProfileInit() {
     InitCrashReporter();
 #endif
 
-#if !defined(OS_CHROMEOS)
-  const base::FilePath kDefaultMtabPath("/etc/mtab");
-  storage_monitor_.reset(new chrome::StorageMonitorLinux(kDefaultMtabPath));
-#endif
-
   ChromeBrowserMainPartsPosix::PreProfileInit();
 }
-
-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
-}