Closed
Bug 1520330
Opened 5 years ago
Closed 5 years ago
Split out NoVsync into two different scenarios
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)
Currently there are two conditions where CONTENT_FRAME_TIME_REASON can be NoVsync. Since, were getting an appreciable amount of these with WebRender it makes sense to split out the telemetry so that we can confirm which scenario we're hitting.
|
Assignee | |
Comment 1•5 years ago
|
||
Currently there are two conditions where CONTENT_FRAME_TIME_REASON can be NoVsync. Since, were getting an appreciable amount of these with WebRender it makes sense to split out the telemetry so that we can confirm which scenario we're hitting.
Pushed by jmuizelaar@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/6f0a657ae73e Split out NoVsync into two different scenarios. r=mattwoodrow
|
||
Comment 3•5 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox66:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla66
|
||
Updated•5 years ago
|
Assignee: nobody → jmuizelaar
You need to log in
before you can comment on or make changes to this bug.
Description
•