Closed
Bug 1649684
Opened 5 years ago
Closed 5 years ago
Make various ProcessHost stop using Google's MessageLoop
Categories
(Core :: IPC, task)
Core
IPC
Tracking
()
RESOLVED
FIXED
mozilla80
| Tracking | Status | |
|---|---|---|
| firefox80 | --- | fixed |
People
(Reporter: jya, Assigned: jya)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
The RDD process manager is using a MessageLoop; it should be using the nsISerialEventTarget instead.
|
Assignee | |
Comment 1•5 years ago
|
||
This change can be applied to all process hosts but the GMP and plugins one.
While they all use internally the IO message loop; they don't need to use it, a nsISerialEventTarget always exists when the IPC channel is opened, and we should be using it to destroy the process host too
Component: Audio/Video: Playback → IPC
Summary: Make RDDProcessHost stop using Google's MessageLoop → Make various ProcessHost stop using Google's MessageLoop
|
|
Assignee | |
Comment 2•5 years ago
|
||
In all those cases, the current nsISerialEventTarget is either the main thread or the MessageChannel's nsISerialEventTarget (since bug 1634846)
Pushed by jyavenard@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/5038a85d05e3
Use the current nsISerialEventTarget with the various process hosts. r=nika
|
||
Comment 4•5 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox80:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla80
You need to log in
before you can comment on or make changes to this bug.
Description
•