Closed Bug 1154273 (loop-e10s) Opened 5 years ago Closed 3 years ago
[meta] Run Loop/ Hello documents in their own content process
Running about:looppanel and about:loopconversation documents in their own content processes yields the following benefits: 1. Processing done for Loop will happen off the main thread. This means that our JS and WebRTC interactions won't block the main thread, preventing freezes and jitter. 2. We'll be able to share e10s (remote) tabs. See bug 1137634. 3. Allows to replace the mozLoop singleton API, exposed in the Loop documents on the navigator objects, with a more robust and scalable message passing architecture. 4. Prevents using CPOWs when there's incoming direct call (global ringer). There are no other unsafe CPOW usages know at this point. This bug will serve as a meta bug to keep track of this work, or: any work that is related to e10s and Loop.
Rank: 25 → 32
Priority: P2 → P3
Whiteboard: [e10s] → [e10s]
Summary: Run Loop/ Hello documents in their own content process → [meta] Run Loop/ Hello documents in their own content process
Depends on: 1253688
Support for Hello/Loop has been discontinued. https://support.mozilla.org/kb/hello-status Hence closing the old bugs. Thank you for your support.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.