Postmortem report collection: validate internal state

components/browser_watcher/stability_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 browser_watcher;
 
@@ skipping 169 matching lines @@
   // A 32-bit identifier for the name of the field trial.
   optional fixed32 name_id = 1;
 
   // A 32-bit identifier for the user's group within the field trial.
   optional fixed32 group_id = 2;
 }
 
 // A stability report contains information pertaining to the execution of a
 // single logical instance of a "chrome browser". It is comprised of information
 // about the system state and about the chrome browser's processes.
-// Next id: 6
+// Next id: 7
 message StabilityReport {
+  // Whether the report is complete. Reports can be incomplete when the
+  // recording size quota is hit.
+  optional bool is_complete = 6;
+
   optional SystemState system_state = 1;
   // TODO(manzagop): revisit whether a single repeated field should contain all
   //     processes, or whether it's preferable to have separate fields per type.
   // TODO(manzagop): add information about the type of process, pid, process
   //     times (e.g. start time), hierarchical relationships (e.g. parent pid),
   //     command line, etc.
   repeated ProcessState process_states = 2;
   // TODO(manzagop): if/when reports contain multiple processes, attribute and
   //     relocate these to their process (and perhaps thread).
   repeated string log_messages = 3;
   map<string, TypedValue> global_data = 4;
 
   // The field trials the user is currently enrolled in.
   repeated FieldTrial field_trials = 5;
 }