Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(426)

Unified Diff: tools/metrics/histograms/histograms.xml

Issue 1084943002: Add UMA stats for hard-fault counts for Windows 7 and greater. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Addressed comments from Erik's review. Created 5 years, 8 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
Download patch
Index: tools/metrics/histograms/histograms.xml
diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml
index 07b69762d4c53a119801626b935ad30a21f75265..2aee8e29eb1334dbe55046cb8485b6a291d418ae 100644
--- a/tools/metrics/histograms/histograms.xml
+++ b/tools/metrics/histograms/histograms.xml
@@ -38050,6 +38050,36 @@ Therefore, the affected-histogram name has to have at least one dot in it.
</summary>
</histogram>
+<histogram name="Startup.BrowserMessageLoopStartHardFaultCount" units="faults">
+ <owner>chrisha@chromium.org</owner>
+ <summary>
+ The number of hard faults incurred in the browser process from startup to
+ start of the main thread's message loop, not including first runs of the
+ browser. This is only reported on Windows 7 and greater.
+ </summary>
+</histogram>
+
+<histogram name="Startup.BrowserMessageLoopStartHardFaultCount.FirstRun"
+ units="faults">
+ <owner>chrisha@chromium.org</owner>
+ <summary>
+ The number of hard faults incurred in the browser process from startup to
+ start of the main thread's message loop on first run. This is only reported
+ on Windows 7 and greater.
+ </summary>
+</histogram>
+
+<histogram name="Startup.BrowserMessageLoopStartHardFaultCount.Success"
+ enum="BooleanSuccess">
+ <owner>chrisha@chromium.org</owner>
+ <summary>
+ If OS support was detected (Windows 7 and greater) indicates whether it was
+ possible to determine the number of hard faults that have occurred in the
+ process from startup to start of the main thread's message loop. This can
+ fail because the underlying call is inherently racy.
+ </summary>
+</histogram>
+
<histogram name="Startup.BrowserMessageLoopStartTime">
<owner>jeremy@chromium.org</owner>
<summary>

Powered by Google App Engine
This is Rietveld 408576698