1379973 - Web Push notifications not triggered in service worker with e10s

Status: RESOLVED DUPLICATE of bug 1369476

(Core :: DOM: Push Subscriptions, defect)

Description

[herrernst]

Most of the time (but not always), "push" events from web push notifications are not dispatched to a service worker when no corresponding origin window is open and e10s is enabled.

Steps to reproduce:
0. Make sure e10s is on
1. Go to https://framework.realtime.co/demo/web-push/ and allow notifications
1a. Copy the curl command for triggering a push notification
2. Close the page, open some other tabs; maybe browser restart is necessary
3. Enter the curl command; notification should be shown, but isn't

Attached is a screencast for better understanding. First, Firefox runs without e10s because of blocking plugins. Notification is received and shown. Then, plugins get disabled and Firefox restarts with e10s on. Notifications are not shown anymore (Wireshark is running in the background to verify reception of push messages).

We have reproduced it on 32bit and 64bit Windows and also on macOS.

Comment 1

[herrernst]

Screencast here: https://herrernst.github.io/webspace/firefox-web-push-service-worker-e10s.mp4

Comment 2

[Ben Kelly [:bkelly, not reviewing]]

We have a known issue on mac where if there are no windows open then we don't handle the push message.  I have not observed this on windows before.

What version of firefox did you observe this on windows?

Comment 3

[Ben Kelly [:bkelly, not reviewing]]

I can't reproduce it so far on my windows 10 machine using the steps in comment 0.  I've tried with FF56 nightly and FF54 release so far.

Comment 4

[herrernst]

As entered in the metadata, it's current stable 54.
I've now uploaded the screencast. As noted, the bug doesn't happen every time, but very often.

Comment 5

[Ben Kelly [:bkelly, not reviewing]]

Ok, I can reproduce now by trying to match the screencast.  It seems that the about:debugging#workers tab seems to cause this to start to happen.

If you close your about:debugging window, does it still reproduce for you?

Comment 6

[herrernst]

It seems to me now that this happens when no "remote content" tab is loaded (excluding "lazy" tabs). If I only have the settings page or new tab page loaded, notifications are not delivered. With the homepage ("about:home"), it still works.

Comment 7

[Ben Kelly [:bkelly, not reviewing]]

I think this is a known issue.  We currently don't have a way to keep the content process alive without a window open, so we can't spawn the service worker.  I can't find the bug, though.  Catalin, do you remember where we have this filed?

Ultimately we will be fixing this as part of our larger refactor in bug 1231208.

Comment 8

[Ben Kelly [:bkelly, not reviewing]]

Sorry, "without a window open" means a "content window open".  Things like about:debugging, etc are not considered content windows and they do not spawn a process.  They run in our parent process instead.

Comment 9

[herrernst]

Ok, thanks for clarifying. So this is probably a minor issue.

Comment 10

[Cătălin Badea (:catalinb)]

There's already a bug for this issue: bug 1369476.