Record Persistent Metrics To The Bitter End |
|
Issue descriptionCurrently, the cleanup of Chrome creates a log of unreported metrics and then deletes the persistent file. This both slows down the shutdown of Chrome and leaves a portion of the process lifetime uncovered with regard to metrics. 1) Don't delete the persistent metrics file. This will collect all metrics until the process actually exits to be reported by a future run of the browser. Because persistent metrics files include a copy of the system profile, they'll be properly associated with the correct run. 2) Don't do the final log collection, trusting that a future run will collect everything and report it correctly.
,
Jan 2 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/aa85f190a8942a819ca1aa54a67dc7abd512c96d commit aa85f190a8942a819ca1aa54a67dc7abd512c96d Author: Brian White <bcwhite@chromium.org> Date: Tue Jan 02 20:04:11 2018 Always keep metrics files on shutdown. Everything went well with the experiment so make it permanent. Bug: 782879 Change-Id: I340fc590d994bac2e50f17b25890558430136365 Reviewed-on: https://chromium-review.googlesource.com/847417 Reviewed-by: Alexei Svitkine <asvitkine@chromium.org> Commit-Queue: Brian White <bcwhite@chromium.org> Cr-Commit-Position: refs/heads/master@{#526526} [modify] https://crrev.com/aa85f190a8942a819ca1aa54a67dc7abd512c96d/chrome/browser/metrics/chrome_metrics_service_client.cc |
|
►
Sign in to add a comment |
|
Comment 1 by bugdroid1@chromium.org
, Nov 10 2017