Open Bug 1432184 Opened 5 years ago Updated 5 months ago

clean up worker LoadGroup handling


(Core :: DOM: Workers, enhancement, P2)





(Reporter: bkelly, Unassigned, NeedInfo)



Currently we have a weird LoadGroup mechanism in worker code.  We try to use the parent's LoadGroup in general.  For things like SharedWorker which may be attached to different clients over time, though, we do a weird overriding mechanism.  We also use this mechanism for ServiceWorkers.

We should perhaps consider simply making workers have their own distinct load group.  The closing of the worker for normal reasons would trigger this load group to be canceled, etc.

Currently we need the parent's load group for a few reasons, though:

1. We need the docshell loadgroup in order for docshell to act as the nsINetworkInterceptController.  After bug 1231211 we will be able to make the worker do this instead.
2. The docshell loadgroup allows devtools to see the top window on any nsIChannel.associatedWindow() so it can be displayed on network monitor.

There may be other issues as well.

It would really clean things up, though, if we could have a single load group setup path for workers without the weird corner cases for different types.
Priority: -- → P2
:bkelley, going to triage as P2 as this seems like a good area for us to tackle next in terms of cleaning up. Let me know what you think.
Flags: needinfo?(bkelly)
In some ways it would be easier to wait on this.  If we had e10s in place on all platforms some of the reasons to keep the loadgroup from the docshell would go away naturally.

In any case, I don't think its an immediate priority.
Flags: needinfo?(bkelly)

:perry, did "some of the reasons" go away? Is there something left to do?

Flags: needinfo?(perry)

The change proposed in the bug description hasn't happened, but I am definitely lacking context on what "some of the reasons" refers to and worker loadgroups in general...

Flags: needinfo?(perry)

Andrew, do you have some more context here?

Flags: needinfo?(bugmail)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.