See the corresponding webrender issue (which will be closed since all of the remaining work is on the gecko side: https://github.com/servo/webrender/issues/2792 We just need to check whether gpu-side memory was purged through extensions like NV_robustness_video_memory_purge and use WebRender's ClearCaches API.

Here is a naive attempt at handling the memory purges. Sotaro what do you think? I don't know if it is worth centralizing the device reset and memory purge in one place since the current support we have talks directly to the d3d device, but you know this stuff a lot better than I do. I haven't properly tested this yet.

Comment on attachment 8986210 [details] [diff] [review] Handle video memory purge with WebRender Review of attachment 8986210 [details] [diff] [review]: ----------------------------------------------------------------- The patch looks good :) The device reset requests to re-create all compositor sessions and updating d3d devices on windows. But memory purge does not request them. Then it seems simpler just to keep them as separate. By the way, it is nice if we could test memory purge like "Trigger Device Reset" in about:support.

Comment on attachment 8986210 [details] [diff] [review] Handle video memory purge with WebRender I kind of forgot about this one. Let's land it.

Pushed by nsilva@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/402e30935941 Handle video memory purge with WebRender. r=sotaro