Open Bug 1369476 Opened 7 years ago Updated 1 year ago

PushEvent is not fired in e10s mode when there are no content processes running


(Core :: DOM: Service Workers, defect, P3)





(Reporter: bkelly, Unassigned)


(Depends on 1 open bug, Blocks 1 open bug)


We should start a process in this case:

We can use this method:


Currently we basically just ignore push events on mac when firefox is open, but we have no content processes because all the windows have been closed.

I feel like there is already a bug on this, but I can't find it.
We should fix this. When does it occur? Only having about:<something> open? On macOS when you have all windows closed but Firefox is still running?
Flags: needinfo?(bkelly)
Priority: -- → P2
Macos with no windows is the main case I'm aware of.
Flags: needinfo?(bkelly)
Having just private browsing windows and receiving push messages might be affected by this bug on other platforms.

Anyhow, fixing this would require being able to keep content processes running for SW instances. To do that we need some sort of abstraction over windows and workers that are considered for the lifetime of a ContentParent. I thought Ben's client patches partially address this - can we fix this now without resorting to a hack?
Oh right.  Its not just starting the process, but keeping it alive.  This probably needs to wait for our multi-e10s refactor.
Moving to p3 because no activity for at least 1 year(s).
See for more information
Priority: P2 → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.