Closed Bug 1889737 Opened 2 years ago Closed 1 month ago

Ensure we don't collect overflowed largest_contentful_paint_from_response_start

Categories

(Core :: Performance Engineering, defect)

defect

Tracking

()

RESOLVED FIXED
153 Branch
Tracking Status
firefox153 --- fixed

People

(Reporter: sefeng211, Assigned: jlink, NeedInfo)

References

(Blocks 1 open bug)

Details

(Whiteboard: [fxpe])

Attachments

(1 file, 1 obsolete file)

No description provided.

We seem to be collecting some overflowed durations based on the Glean
data. This is a sanity check for that.

Assignee: nobody → sefeng
Status: NEW → ASSIGNED

The severity field is not set for this bug.
:fdoty, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(fdoty)
Severity: -- → S3
Flags: needinfo?(fdoty)

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.

Flags: needinfo?(sean)

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: sean → jlink
Attachment #9395118 - Attachment is obsolete: true
Attachment #9586455 - Attachment description: Bug 1889737: Ensure that we don't report a negative largest_contentful_paint_from_response_start r=denispal,bas → Bug 1889737: Ensure that we don't report an underflowed values in largest_contentful_paint_* metrics r=denispal,bas
Attachment #9586455 - Attachment description: Bug 1889737: Ensure that we don't report an underflowed values in largest_contentful_paint_* metrics r=denispal,bas → Bug 1889737: Ensure that we don't report underflowed values in largest_contentful_paint_* metrics r=denispal,bas
Pushed by jlink@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/121593b924f0 https://hg.mozilla.org/integration/autoland/rev/4df68b9f93bd Ensure that we don't report underflowed values in largest_contentful_paint_* metrics r=denispal
Status: ASSIGNED → RESOLVED
Closed: 1 month ago
Resolution: --- → FIXED
Target Milestone: --- → 153 Branch
Whiteboard: [fxpe]
QA Whiteboard: [qa-triage-done-c154/b153]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: