Closed
Bug 1165359
Opened 9 years ago
Closed 7 years ago
BHR histograms in about:telemetry are rendered incorrectly
Categories
(Toolkit :: Telemetry, defect, P4)
Toolkit
Telemetry
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: vladan, Unassigned)
References
Details
(Whiteboard: [measurement:client])
Attachments
(1 file)
(deleted),
image/png
|
Details |
The height of BHR histograms in "Thread Hangs" is always zero. This is a regression from bug 1122480
Comment 1•9 years ago
|
||
What is a good way to trigger some histograms there?
Flags: needinfo?(vdjeric)
Reporter | ||
Comment 2•9 years ago
|
||
(In reply to Georg Fritzsche [:gfritzsche] from comment #1) > What is a good way to trigger some histograms there? The BHR hang threshold is 128ms so browsing for a little while (especially heavy pages with Flash) will do it. Doing a tight loop from DevTools should do it too.
Flags: needinfo?(vdjeric)
Comment 3•9 years ago
|
||
Even with a heavy loop in the browser console i'm failing to trigger something showing up in Services.telemetry.chromeHangs. Any tips on consistent steps to trigger data there?
Reporter | ||
Comment 4•9 years ago
|
||
(In reply to Georg Fritzsche [:gfritzsche] from comment #3) > Even with a heavy loop in the browser console i'm failing to trigger > something showing up in Services.telemetry.chromeHangs. > > Any tips on consistent steps to trigger data there? It's in the "Thread Hangs" section (Services.telemetry.threadHangStats), not "Browser Hangs" (Services.telemetry.chromeHangs)
Updated•9 years ago
|
Updated•9 years ago
|
Priority: -- → P3
Updated•9 years ago
|
Points: --- → 1
Whiteboard: [measurement:client]
Updated•8 years ago
|
Priority: P3 → P4
Comment 5•7 years ago
|
||
Hello! Is this bug still relevant? I tried the above mentioned methods to trigger histograms, but nothing happened. Could someone please guide me through replicating and understanding the issue?
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•