Remove the chromium event loop

NEW
Unassigned

Status

()

Core
IPC
P3
normal
2 years ago
3 months ago

People

(Reporter: khuey, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: btpp-backlog)

Our unholy combination of different event loops is an enormous pain, leading to everything from confusion (should I be using nsIRunnable or Task?) to outright bugs (when people don't realize that events of different types aren't necessarily ordered, or that PostDelayedTask is ... weird). We will unify around the XPCOM event loop/thread/etc machinery.
Whiteboard: btpp-active

Updated

2 years ago
Depends on: 1265951

Updated

2 years ago
Depends on: 1273631
On XPCOM threads, the chromium event loop now just passes through dispatches to the XPCOM event queue.

For threads that are not XPCOM threads, we should make them XPCOM threads.  For the chromium threads that need special event processing logic (e.g. the IO thread, the miscellaneous UI threads) we should dispatch a runnable that runs some custom logic and calls NS_Process[Next|Pending]Events when appropriate to run the XPCOM event queue.
Assignee: khuey → nobody

Updated

11 months ago
Priority: -- → P2
Whiteboard: btpp-active → btpp-backlog

Updated

5 months ago
Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.