Ensure we don't collect overflowed largest_contentful_paint_from_response_start
Categories
(Core :: Performance Engineering, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox153 | --- | fixed |
People
(Reporter: sefeng211, Assigned: jlink, NeedInfo)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fxpe])
Attachments
(1 file, 1 obsolete file)
| Reporter | ||
Comment 1•2 years ago
|
||
We seem to be collecting some overflowed durations based on the Glean
data. This is a sanity check for that.
Updated•2 years ago
|
Comment 2•2 years ago
|
||
The severity field is not set for this bug.
:fdoty, could you have a look please?
For more information, please visit BugBot documentation.
Updated•2 years ago
|
Comment 3•1 month ago
|
||
The following patch is waiting for review from an inactive reviewer:
| ID | Title | Author | Reviewer Status |
|---|---|---|---|
| D206689 | Bug 1889737 - Ensure we don't collect overflowed largest_contentful_paint_from_response_start | sefeng211 | bas: Disabled |
:sefeng211, could you please find another reviewer or abandon the patch if it is no longer relevant?
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 4•1 month ago
|
||
According to Claude and ChatGPT, this could be caused by precision reduction in GetLargestContentfulRenderTimeStamp(). I was able to reproduce this scenario by setting privacy.resistFingerprinting.reduceTimerPrecision.microseconds to a large value in about:config and reloading example.com a few times.
One way to fix this would be to use a high-res timestamp instead but, while I'm not an expert in the world of fingerprinting, this seems like it would potentially make LCP times able to be used for fingerprinting.
So, at least for the moment, I am in favor of something similar to sefeng's patch here but, rather than completely bail on reporting LCP for this case, we should just report an LCP of zero (since that is an appropriate approximation of the correct answer).
I will put up a patch for that shortly.
| Assignee | ||
Updated•1 month ago
|
Updated•1 month ago
|
| Assignee | ||
Comment 5•1 month ago
|
||
Updated•1 month ago
|
Updated•1 month ago
|
Updated•23 days ago
|
Updated•23 days ago
|
Updated•17 days ago
|
Description
•