Leak reports collect information about the memory usage

chrome/browser/metrics/leak_detector/leak_detector_controller_unittest.cc

Index: chrome/browser/metrics/leak_detector/leak_detector_controller_unittest.cc
diff --git a/chrome/browser/metrics/leak_detector/leak_detector_controller_unittest.cc b/chrome/browser/metrics/leak_detector/leak_detector_controller_unittest.cc
index f900f216d646e3476e2e0019b88a43b0a3012444..23695d6ae71dcb9232bde6b3a527579024251ede 100644
--- a/chrome/browser/metrics/leak_detector/leak_detector_controller_unittest.cc
+++ b/chrome/browser/metrics/leak_detector/leak_detector_controller_unittest.cc
@@ -32,7 +32,10 @@ class TestLeakDetectorController : public LeakDetectorController {
  public:
   using LeakDetectorController::OnLeaksFound;
 
-  TestLeakDetectorController() {}
+  // This constructor suppresses starting memory metrics job in the superclass.
+  TestLeakDetectorController() {
+    LeakDetectorController::waiting_for_collect_memory_usage_ = true;

[Simon Que, 2016/10/07 06:24:58]

You have the right idea but this is not the best design pattern. This is a state
variable that you're treating like an initialization flag.

Instead, create a separate boolean in LeakDetectorController to indicate whether
memory usage info should be collected. Initialize that to true by default, and
then set it to false here.

[mwlodar, 2016/10/07 18:54:35]

Done.

+  }
 
  private:
   DISALLOW_COPY_AND_ASSIGN(TestLeakDetectorController);