While looking at Arstechnica's performance issues, we noticed that TextureClient's destructor fires on the main thread (intentionally), but unintentionally this frees the DrawTarget on the main thread as well. This frees D2D resources and causes lock contention with the paint thread. It's not super serious, but we should see if we can make the D2D resources get allocated and freed on the paint thread instead.
status-firefox57: --- → unaffected
Summary: TextureClients can use D2D on the main thread → TextureClients can use D2D on the main thread (relevant with OMTP)
Destruction portion of this was done in bug 1422169.
You need to log in before you can comment on or make changes to this bug.