Adding Memory.TabFootprint UKM events.
Memory.TabFootprint events give a high-level sample of how much memory
is used to render a given URL. To keep these events easy to reason about
and analyze, some memory isn't accounted for. Namely, when processes
host parts of other tabs, we don't record their contributions. We do,
however, make sure that an individual record has all the information
nescessary to classify it as a full or partial record.
Change-Id: If7a19031502e357be9567ebed760de234f2974ac
Reviewed-on: https://chromium-review.googlesource.com/c/1191817
Reviewed-by: Kentaro Hara <[email protected]>
Reviewed-by: Timothy Dresser <[email protected]>
Reviewed-by: Ken Buchanan <[email protected]>
Reviewed-by: Steven Holte <[email protected]>
Commit-Queue: Tom McKee <[email protected]>
Cr-Commit-Position: refs/heads/master@{#601136}diff --git a/chrome/browser/BUILD.gn b/chrome/browser/BUILD.gn
index 3a8bc8c..df9532c 100644
--- a/chrome/browser/BUILD.gn
+++ b/chrome/browser/BUILD.gn
@@ -790,6 +790,8 @@
"metrics/sampling_metrics_provider.h",
"metrics/subprocess_metrics_provider.cc",
"metrics/subprocess_metrics_provider.h",
+ "metrics/tab_footprint_aggregator.cc",
+ "metrics/tab_footprint_aggregator.h",
"metrics/testing/metrics_reporting_pref_helper.cc",
"metrics/testing/metrics_reporting_pref_helper.h",
"metrics/thread_watcher.cc",
