tools/metrics/histograms/histograms.xml - Issue 1980743002: Track thread activities in order to diagnose hangs.

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

Issue 1980743002: Track thread activities in order to diagnose hangs. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@readwrite-mmf

Patch Set: addressed minor review comments; added ownership Created 4 years, 5 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 06532ba140819f137bad3e921a9721d53e544c64..3b205b2f84e94114c33f062d8a89e66a73e89f0c 100644

--- a/tools/metrics/histograms/histograms.xml

+++ b/tools/metrics/histograms/histograms.xml

@@ -60197,6 +60197,26 @@ http://cs/file:chrome/histograms.xml - but prefer this file for new entries.

</summary>

</histogram>

+<histogram name="UMA.ActivityTracker.ThreadTrackers.Count">

Alexei Svitkine (slow) 2016/08/02 21:18:51 Add units= to both of these.

bcwhite 2016/08/04 14:06:20 Done.

+ <owner>bcwhite@chromium.org</owner>

+ <summary>

+ The number of threads being tracked for activities. This value is updated

Alexei Svitkine (slow) 2016/08/02 21:18:51 "tracked for activities" is meaningless to someone

bcwhite 2016/08/04 14:06:20 Done.

+ every time a new thread gets an activity tracked for the first time so will

+ show one count for every permanent thread but multiple counts for a thread

+ than exits and is replaced.

+ </summary>

+</histogram>

+<histogram name="UMA.ActivityTracker.ThreadTrackers.MemLimitTrackerCount">

Alexei Svitkine (slow) 2016/08/02 21:18:51 These histograms don't seem to be related to the U

bcwhite 2016/08/04 14:06:20 "Debug.*" okay?

+ <owner>bcwhite@chromium.org</owner>

+ <summary>

+ The limit on the number of thread trackers that could be allocated from the

+ persistent memory segment. Trackers beyond this number were allocated from

+ the heap and thus were not available for analysis. This value is updated on

+ every "memory full" failure.

+ </summary>

+</histogram>

<owner>asvitkine@chromium.org</owner>

« chrome/browser/chrome_browser_field_trials_desktop.cc ('K') | « chrome/browser/chrome_browser_field_trials_desktop.cc ('k') | no next file » | no next file with comments »