Leak reports collect information about the last uptrend

components/metrics/proto/memory_leak_report.proto

Index: components/metrics/proto/memory_leak_report.proto
diff --git a/components/metrics/proto/memory_leak_report.proto b/components/metrics/proto/memory_leak_report.proto
index 1a998fefa0b8a18bebf88cb4a5536e7421c10480..2e3d7b7a8db9cab20a24224951c7437e944bbb93 100644
--- a/components/metrics/proto/memory_leak_report.proto
+++ b/components/metrics/proto/memory_leak_report.proto
@@ -109,7 +109,9 @@ message MemoryLeakReportProto {
   //
   // |num_rising_intervals| equals timeslot_now - timeslot_drop,
   // where timeslot_drop is the timeslot number of the last frame that saw
-  // a drop in the number of allocations (or 0 if there were no drops).
+  // a drop in the number of allocations, or the first frame in the history
+  // if there were no drops (history is cleared when the net number of
+  // allocations hits 0).

[Alexei Svitkine (slow), 2016/10/14 20:04:45]

Please make this change in google3 first before landing this, so the files are
in sync. If it's your last day today, sounds like your host needs to make this
change.

[Simon Que, 2016/10/14 21:06:28]

I am the host. I will take care of it in google3.

   // If it is < 32, it will be visible in the allocation history graph.
   // If it is >= 32, it will not be seen in the graph.
   // E.g. for history [3,2,4,4,7] |num_rising_intervals| equals 3.