Move memory histograms generation to MetricsMemoryDetails.
Also moves MetricsMemoryDetails (and MemoryGrowthTracker) to its
own file as well as moving the corresponding browser test.
This allows the base MemoryDetails class to be simplified, as it now
needs to do a lot less. Also, disables logging of these histograms
from a couple places that use the MemoryDetails that didn't need to
log the histograms but were doing it anyways (with TODOs).
BUG=448834
Review URL: https://codereview.chromium.org/823533004
Cr-Commit-Position: refs/heads/master@{#312026}
diff --git a/chrome/browser/memory_details_win.cc b/chrome/browser/memory_details_win.cc
index 5ef4789..8e175cd 100644
--- a/chrome/browser/memory_details_win.cc
+++ b/chrome/browser/memory_details_win.cc
@@ -37,9 +37,7 @@
MAX_BROWSERS
} BrowserProcess;
-MemoryDetails::MemoryDetails()
- : user_metrics_mode_(UPDATE_USER_METRICS),
- memory_growth_tracker_(NULL) {
+MemoryDetails::MemoryDetails() {
base::FilePath browser_process_path;
PathService::Get(base::FILE_EXE, &browser_process_path);
const base::string16 browser_process_name =
