Closed Bug 1494206 Opened Last year Closed Last year

Update webrender to 0d2e9611c07e04ac830277f16a3b46bf125b9e7c


(Core :: Graphics: WebRender, enhancement, P3)

64 Branch



Tracking Status
firefox64 --- fixed


(Reporter: darkspirit, Assigned: jrmuizel)


(Blocks 1 open bug, )


(Whiteboard: [gfx-noted])


(1 file)

+++ This bug was initially created as a clone of Bug #1494042 +++

I'm filing this as a placeholder bug for the next webrender update. I may be running a cron script [1] that does try pushes with webrender update attempts, so that we can track build/test breakages introduced by webrender on a rolling basis. This bug will hold the try push links as well as dependencies filed for those breakages, so that we have a better idea going into the update of what needs fixing. I might abort the cron job because once things get too far out of sync it's hard to fully automate fixing all the breakages.

When we are ready to actually land the update, we can rename this bug and use it for the update, and then file a new bug for the next "future update".

I attached a patch that updates the Gecko reftest expectations for WebRender PR #3126 (blur support).
Pushed by
Update webrender to commit 0d2e9611c07e04ac830277f16a3b46bf125b9e7c
Update tests for blur changes.
Closed: Last year
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
Alias: wr-future-update
Assignee: nobody → jmuizelaar
Summary: Future webrender update bug → Update webrender to 0d2e9611c07e04ac830277f16a3b46bf125b9e7c
Big performance improvements thanks to this bug!

== Change summary for alert #16226 (as of Fri, 28 Sep 2018 01:01:06 GMT) ==


 23%  tscrollx linux64-qr opt e10s stylo                    3.05 -> 2.35
  7%  displaylist_mutate windows10-64-qr opt e10s stylo     5,416.81 -> 5,012.33
  6%  displaylist_mutate linux64-qr opt e10s stylo          5,228.94 -> 4,905.66
  5%  tp5o_scroll windows10-64-qr opt e10s stylo            2.95 -> 2.80
  3%  tps windows10-64-qr opt e10s stylo                    10.17 -> 9.82

For up to date results, see:
You need to log in before you can comment on or make changes to this bug.