Have CONTENT_FRAME_TIME_REASON correspond to CONTENT_FRAME_TIME_VSYNC

RESOLVED FIXED in Firefox 66

Status

()

enhancement
RESOLVED FIXED
5 months ago
5 months ago

People

(Reporter: jrmuizel, Assigned: jrmuizel)

Tracking

unspecified
mozilla66
Points:
---

Firefox Tracking Flags

(firefox66 fixed)

Details

Attachments

(1 attachment)

Assignee

Description

5 months ago
CONTENT_FRAME_TIME_VSYNC is more meaningful metric because it actually starts at the beginning of the vsync making it easier to reason about missing frames. It makes more sense for CONTENT_FRAME_TIME_REASON wants to use this same starting point.
Assignee

Comment 1

5 months ago
CONTENT_FRAME_TIME_VSYNC is more meaningful metric because it actually
starts at the beginning of the vsync making it easier to reason about
missing frames. It makes more sense for CONTENT_FRAME_TIME_REASON wants
to use this same starting point.

Comment 3

5 months ago
Pushed by jmuizelaar@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/f55412c54286
Have CONTENT_FRAME_TIME_REASON correspond to CONTENT_FRAME_TIME_VSYNC. r=mattwoodrow

Comment 4

5 months ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/f55412c54286
Status: NEW → RESOLVED
Last Resolved: 5 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla66
Assignee: nobody → jmuizelaar
You need to log in before you can comment on or make changes to this bug.