Add build ID field to MemoryLeakReportProto

components/metrics/proto/memory_leak_report.proto

 // Copyright 2016 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 syntax = "proto2";
 
 option optimize_for = LITE_RUNTIME;
 
 package metrics;
 
-// Next tag: 6
+// Next tag: 7
 message MemoryLeakReportProto {
   // The call stack at which the leak was found. This is a list of offsets
   // within the program binary. The first entry is the deepest level of the call
   // stack.
   //
   // Some call stack entries may not be within the Chrome binary (e.g.
   // JavaScript code). Those entries are given as the absolute offset in memory.
   //
   // The offsets within Chrome are determined by whether the original call stack
   // address was within the executable region of the Chrome binary's mapping in
@@ skipping 40 matching lines @@
   optional Params params = 3;
 
   // The type of Chrome process on which this leak report was generated.
   enum ProcessType {
     UNKNOWN_PROCESS = 0;
     BROWSER_PROCESS = 1;
     RENDERER_PROCESS = 2;
   }
   optional ProcessType source_process = 5;
 
+  // The build ID of the Chrome binary from which this leak report was obtained.
+  // The build ID is typically a 16- or 20-byte hash that is generated by the
+  // compiler that built the binary. This value will be read directly from the
+  // GNU build notes section of the Chrome binary.
+  optional bytes build_id = 6;
+
   //////////////////////////////////////////////////////////////////////////////
 
   // Represents a single snapshot of the internal bookkeeping of the Runtime
   // Memory Leak Detector, which tracks the number of extant allocations (a
   // block of heap memory that has been allocated but not yet freed).
   //
   // Next tag: 3
   message AllocationBreakdown {
     // Table of number of extant allocations for each allocation size. The i-th
     // entry in the vector is the net number of allocations for sizes in the
     // range [i * 4, i * 4 + 3].
     repeated uint32 counts_by_size = 1;
 
     // The number of extant allocations with size = |size_bytes| and made from
     // the call site given by |call_stack|. If it is not set, it means tracking
     // of allocs per call site for allocation size = |size_bytes| has not yet
     // begun at the time of this entry.
     optional uint32 count_for_call_stack = 2;
   }
 
   // A record of past allocation data leading up to the circumstances that
   // generated the current leak report.
   //
   // A new snapshot is taken every |analysis_interval_bytes| of memory
   // allocation. The oldest record is at the beginning. The most recent record,
   // taken at the time the report was generated, is at the end.
   repeated AllocationBreakdown alloc_breakdown_history = 4;
 }