Closed Bug 1498897 Opened 1 year ago Closed 1 year ago
Update webrender to 98d507003c07c003ef0e0297dc4d29ee896a5868
+++ This bug was initially created as a clone of Bug #1498650 +++ 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
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/bd4c433b0e50 Update webrender to commit 98d507003c07c003ef0e0297dc4d29ee896a5868
AWSY improvements noticed! \o/ == Change summary for alert #16888 (as of Tue, 16 Oct 2018 16:53:51 GMT) == Improvements: 6% Heap Unclassified linux64-qr opt stylo 290,934,225.35 -> 274,569,644.29 3% Explicit Memory linux64-qr opt stylo 566,560,640.92 -> 552,296,146.98 For up to date results, see: https://treeherder.mozilla.org/perf.html#/alerts?id=16888
Interesting - the only thing significant in that sync is . There's no corresponding drop on windows, and it's a 15MB drop in unclassified heap memory, so my best guess is that we're somehow eliminating a heap-allocation in the linux driver. Glenn, is that plausible?  https://github.com/servo/webrender/pull/3197
I would be surprised if that change resulted in a memory reduction. It's possible, but unlikely. What were the other changes?
(In reply to Glenn Watson [:gw] from comment #6) > I would be surprised if that change resulted in a memory reduction. It's > possible, but unlikely. What were the other changes? See the URL field of this bug. Anyway, not super important.
You need to log in before you can comment on or make changes to this bug.