We want to improve things more before we can do this well.

Andrew can you look at doing this?

Need to refresh uplift to beta once this makes its way into nightly.

Backed out changeset e1c031719669 (bug 1638011) for Build bustages. CLOSED TREE

Log:
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=302377698&repo=autoland&lineNumber=20021

Push with failures:
https://treeherder.mozilla.org/#/jobs?repo=autoland&group_state=expanded&revision=e1c031719669a930f0fc61a5ec1060237b1cee3c

Backout:
https://hg.mozilla.org/integration/autoland/rev/dc88ebc9fed6b2b7330816947c32a72ef65b69f9

Why does win32 use a different calling convention..... today I learned. Waiting try build to come back green for target.

https://hg.mozilla.org/mozilla-central/rev/47219a623fca

Comment on attachment 9149220 [details]
Bug 1638011 - Block WebRender in release for high refresh rate monitors.

Beta/Release Uplift Approval Request

• User impact if declined: WebRender may not work as well at higher refresh rates. This change mitigates that risk.
• Is this code covered by automated tests?: Yes
• Has the fix been verified in Nightly?: No
• Needs manual test from QE?: No
• If yes, steps to reproduce:
• List of other uplifts needed: None
• Risk to taking this patch: Low
• Why is the change risky/not risky? (and alternatives if risky): Very low, in the worst case WebRender would just be turned off in the wrong places.
• String changes made/needed:

Comment on attachment 9149220 [details]
Bug 1638011 - Block WebRender in release for high refresh rate monitors.

Low risk mitigation, uplift approved for beta before RC, thanks.

https://hg.mozilla.org/releases/mozilla-beta/rev/198251da7ee3