Closed
Bug 1517980
Opened 6 years ago
Closed 6 years ago
Have CONTENT_FRAME_TIME_REASON correspond to CONTENT_FRAME_TIME_VSYNC
Categories
(Core :: Graphics: WebRender, enhancement)
Core
Graphics: WebRender
Tracking
()
RESOLVED
FIXED
mozilla66
| Tracking | Status | |
|---|---|---|
| firefox66 | --- | fixed |
People
(Reporter: jrmuizel, Assigned: jrmuizel)
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
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•6 years 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 2•6 years 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•6 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox66:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla66
|
||
Updated•6 years ago
|
Assignee: nobody → jmuizelaar
You need to log in
before you can comment on or make changes to this bug.
Description
•