Closed Bug 1500033 Opened 2 years ago Closed 2 years ago
Update webrender to b648c76e2dc2cbcbd635322cdf94ab9d5320e0c1
+++ This bug was initially created as a clone of Bug #1499786 +++ I'm filing this as a placeholder bug for the next webrender update. I may be running a cron script  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".  https://github.com/staktrace/moz-scripts/blob/master/try-latest-webrender.sh
2 years ago
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/40218adf6ccf Update webrender to cset b648c76e2dc2cbcbd635322cdf94ab9d5320e0c1.
Noticed some AWSY improvements! \0/ == Change summary for alert #17003 (as of Mon, 22 Oct 2018 03:39:29 GMT) == Improvements: 6% Heap Unclassified linux64-qr opt stylo 284,066,364.51 -> 268,300,838.95 3% Explicit Memory linux64-qr opt stylo 564,478,616.12 -> 549,610,162.13 2% Resident Memory windows10-64-qr opt stylo 761,104,952.03 -> 744,863,443.19 For up to date results, see: https://treeherder.mozilla.org/perf.html#/alerts?id=17003
You need to log in before you can comment on or make changes to this bug.