Closed
Bug 1634254
Opened 5 years ago
Closed 5 years ago
Remove the need for ipc::MessageLoop
Categories
(Core :: IPC, enhancement)
Core
IPC
Tracking
()
RESOLVED
DUPLICATE
of bug 1260828
People
(Reporter: jya, Unassigned)
References
Details
We have this weird incestuous relationship between XPCOM thread and ipc::MessageLoop
An nsThread set a MessageLoop and similarly, MessageLoop uses an XPCOM thread.
We should remove it all, and use a standard xpcom nsISerialEventTarget instead (nsThread or TaskQueue)
Comment 1•5 years ago
|
||
This looks like a duplicate of bug 1260828. As I understand it (which isn't as well as I'd like), the Chromium and XPCOM event-loop worlds used to be more separate and the current situation is the result of a certain amount of work towards eventually unifying them. I don't think anything significant has happened to it since Kyle Huey left.
See Also: → 1260828
Reporter | ||
Comment 2•5 years ago
|
||
you're right; it is the same.
The use of MessageLoop is really messy
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•