Closed Bug 1513657 Opened 8 months ago Closed 8 months ago

CONTENT_FRAME_TIME is now using the refresh driver tick start time instead of the transaction start

Categories

(Core :: Graphics: WebRender, defect, P2)

defect

Tracking

()

RESOLVED FIXED
mozilla66
Tracking Status
firefox-esr60 --- unaffected
firefox64 --- unaffected
firefox65 --- wontfix
firefox66 --- fixed

People

(Reporter: mattwoodrow, Assigned: mattwoodrow)

References

(Blocks 1 open bug)

Details

(Keywords: regression)

Attachments

(1 file)

This is a regression from  bug 1510853, where I added CONTENT_FRAME_TIME_REASON (which intentionally uses the refresh driver tick start), and it clobbers the value used by CONTENT_FRAME_TIME.
Keywords: regression
Priority: -- → P2
Pushed by mwoodrow@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/2d581255f6d4
Record CONTENT_FRAME_TIME_REASON after CONTENT_FRAME_TIME so that we don't clobber the calculations. r=jrmuizel
https://hg.mozilla.org/mozilla-central/rev/2d581255f6d4
Status: NEW → RESOLVED
Closed: 8 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla66
You need to log in before you can comment on or make changes to this bug.