Metrics provider for statistical stack profiler

chrome/browser/metrics/chrome_metrics_service_client.cc

Index: chrome/browser/metrics/chrome_metrics_service_client.cc
diff --git a/chrome/browser/metrics/chrome_metrics_service_client.cc b/chrome/browser/metrics/chrome_metrics_service_client.cc
index 8954197117c9b35a4d1ba0d4a5d44bf6d59bf963..095a2c3e8d44dbfd28ddc956471377f57979dd39 100644
--- a/chrome/browser/metrics/chrome_metrics_service_client.cc
+++ b/chrome/browser/metrics/chrome_metrics_service_client.cc
@@ -21,6 +21,7 @@
 #include "chrome/browser/browser_process.h"
 #include "chrome/browser/chrome_notification_types.h"
 #include "chrome/browser/google/google_brand.h"
+#include "chrome/browser/metrics/call_stack_profile_metrics_provider.h"
 #include "chrome/browser/metrics/chrome_stability_metrics_provider.h"
 #include "chrome/browser/metrics/omnibox_metrics_provider.h"
 #include "chrome/browser/ui/browser_otr_state.h"
@@ -293,6 +294,11 @@ void ChromeMetricsServiceClient::Initialize() {
   metrics_service_->RegisterMetricsProvider(
       scoped_ptr<metrics::MetricsProvider>(profiler_metrics_provider_));
 
+  call_stack_profile_metrics_provider_ = new CallStackProfileMetricsProvider;

[Ilya Sherman, 2015/03/10 01:44:46]

I don't see any reason to cache this pointer (nor the one above, honestly).  Do
you?

Note: If it *is* important to cache it, then please make sure to initialize the
variable in the constructor.  And, yeah, we should probably initialize the other
profiler var as well, if we keep it around.

[Mike Wittman, 2015/03/16 23:55:15]

No, removed.
All the other metrics providers are referenced within the class. I added
initializers for them.

+  metrics_service_->RegisterMetricsProvider(
+      scoped_ptr<metrics::MetricsProvider>(
+          call_stack_profile_metrics_provider_));
+
 #if defined(OS_ANDROID)
   metrics_service_->RegisterMetricsProvider(
       scoped_ptr<metrics::MetricsProvider>(