1604679 - Service Worker logs don't show up in Console for some debug sessions

Status: RESOLVED DUPLICATE of bug 1429805

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

Description

[:Harald Kirschner :digitarald]

STR:

• Open a new tab with https://firefox-devtools-waiting-sw.glitch.me/
• Open Console
• Repeat until no log appear (Close tab)

AR: No logs
ER: Logs for different SW phases

I assume, with limited technical understanding, that in some cases the SW is on a different process and logs are not captured for that process.

Comment 1

[:Harald Kirschner :digitarald]

Julian, if I remember correctly this was a discussion in Slack. Do you know what the next action was to make this work, or if this was blocked by Fission?

Comment 2

[:Harald Kirschner :digitarald]

Maybe we should dupe against bug 1429805, still gathering feedback.

Comment 3

[Julian Descottes [:jdescottes]]

I think your analysis is correct, and sometimes the sw will run in the same process as the content page (and therefore logs show up in the console), sometimes it doesn't.

By the way I suppose that the logs you are expecting are the ones that show up after clicking on "update", eg

11:00:50.615             v21 pending             sw.js:3:9
11:00:50.619             v21 installing [object ExtendableEvent]             sw.js:6:11
11:00:52.619             v21 installed [object ServiceWorkerGlobalScope]             sw.js:9:15

I remember Perry mentioned that they could enforce running the sw in the same process as the content page? That would be one way of fixing this. Otherwise, more involved solutions are already discussed in the bug you found, Bug 1429805.

Comment 4

[Julian Descottes [:jdescottes]]

I quickly tested this by adding the PID/targetId as the title of the message, and we can verify that the messages logged in the regular content console are the ones emitted in the same process as the content page.