Stop using a background taskqueue with ImageBridgeChild
Categories
(Core :: Graphics: Layers, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr68 | --- | unaffected |
firefox-esr78 | --- | unaffected |
firefox78 | --- | unaffected |
firefox79 | --- | unaffected |
firefox80 | --- | fixed |
People
(Reporter: jya, Assigned: jya)
References
(Depends on 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(1 file)
ImageBridgeChild thread is used for sync-dispatch by the CompositableClient and others.
A background taskqueue is using a threadpool made of a single thread.
This means that no consumers of CompositableClient (e.g. anything dealing with images) can be using a background taskqueue while the ImageBridgeChild itself is using a background taskqueue (see bug 1650352).
Until bug 1650352 is resolved; it's better to have the ImageBridgeChild use a nsThread instead; reverting the changes done in bug 1647628
Assignee | ||
Comment 1•5 years ago
|
||
This is a partial revert of bug 1647628.
The ImageBridgeChild's thread is used to dispatch synchronous tasks by its consumers.
While the background taskqueue is using a single thread threadpool, this would prevent many places to also use a background taskqueue that could end up calling the ImageBridgeChild.
Additionally, we simplify the ShutdownStep1, ShutdownStep2 and fully shutdown the thread in order to remove a thread leak (as there would be a cycle with the nsThreadManager)
Comment 2•5 years ago
|
||
Set release status flags based on info from the regressing bug 1647628
Updated•5 years ago
|
Comment 4•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Description
•