Open
Bug 1397310
Opened 7 years ago
Updated 2 years ago
TextureClients can use D2D on the main thread (relevant with OMTP)
Categories
(Core :: Graphics: Layers, enhancement, P3)
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox57 | --- | unaffected |
People
(Reporter: dvander, Unassigned)
References
Details
(Whiteboard: [gfx-noted])
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.
|
||
Updated•7 years ago
|
Priority: -- → P3
Whiteboard: [gfx-noted]
|
|
||
Updated•7 years ago
|
status-firefox57:
--- → unaffected
Summary: TextureClients can use D2D on the main thread → TextureClients can use D2D on the main thread (relevant with OMTP)
|
||
Comment 1•7 years ago
|
||
Destruction portion of this was done in bug 1422169.
|
||
Comment 2•2 years ago
|
||
The bug assignee didn't login in Bugzilla in the last 7 months.
:bhood, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee: dvander → nobody
Status: ASSIGNED → NEW
Flags: needinfo?(bhood)
|
||
Updated•2 years ago
|
Flags: needinfo?(bhood)
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•