Closed
Bug 1081924
Opened 10 years ago
Closed 6 years ago
negative firstPaint value in telemetry pings
Categories
(Toolkit :: Telemetry, defect, P1)
Tracking
()
RESOLVED
FIXED
People
(Reporter: rvitillo, Assigned: chutten)
References
Details
I have encountered few negative firstPaint values when analyzing telemetry submissions from Release (about one every 20000 submissions). Irving, do you have by chance an idea of why that might happen?
Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(irving)
Comment 1•10 years ago
|
||
For firstPaint I don't have any specific ideas; those values are recorded by StartupTimeline (http://dxr.mozilla.org/mozilla-central/source/toolkit/components/startup/StartupTimeline.h#15), so the next step would be to check if those values are reported by subtracting two time stamps, and whether those time stamps are affected by system clock adjustments (JS Date.now() is, for example).
Flags: needinfo?(irving)
Assignee | ||
Comment 2•6 years ago
|
||
0.0016847% of main_summary pings received on 2018-08-01 had either simpleMeasurements' firstPaint or the scalar timestamps.first_paint with a value less than 1. (The scalar is a uint so negative values would be clamped to 0) This is nicely below the noise threshold so I think we can ignore it.
Assignee: nobody → chutten
Status: NEW → RESOLVED
Points: --- → 1
Closed: 6 years ago
Priority: P3 → P1
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•