Closed
Bug 1226434
Opened 9 years ago
Closed 6 years ago
A content process should run while it has active service workers
Categories
(Core :: DOM: Service Workers, defect, P2)
Core
DOM: Service Workers
Tracking
()
RESOLVED
DUPLICATE
of bug 1438945
Tracking | Status | |
---|---|---|
firefox45 | --- | affected |
People
(Reporter: catalinb, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: SW-MUST)
Regardless if we decide to use a dedicated process or not, we need a mechanism that prevents a content process from shutting down while it has running service workers.
The immediate benefit would be that we can support push notifications on e10s when there are not content processes running.
The solution I have in mind for this is to add an ipc protocol for ServiceWorkerPrivate that's managed by PContent. PContent will keep the process running as long as there are service worker actors, the same way it works for managed pbrowsers.
Comment 1•9 years ago
|
||
Can we just use PBackground instead of a new PContent main thread protocol?
Updated•7 years ago
|
Priority: -- → P5
Updated•6 years ago
|
Blocks: ServiceWorkers-e10s
Whiteboard: SW-MUST
Updated•6 years ago
|
Priority: P5 → P2
Updated•6 years ago
|
QA Whiteboard: SW-MUST
Comment 2•6 years ago
|
||
This mechanism is implemented by SharedWorker remoting in bug 1438945.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•