Skip to content

should "protected worker" concept check for BroadcastChannel? #3993

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wanderview opened this issue Sep 4, 2018 · 2 comments
Open

should "protected worker" concept check for BroadcastChannel? #3993

wanderview opened this issue Sep 4, 2018 · 2 comments

Comments

@wanderview
Copy link
Member

Currently the "protected worker" concept lists a number of conditions:

https://html.spec.whatwg.org/multipage/workers.html#protected-worker

A worker is said to be a protected worker if it is an active needed worker and either it has outstanding timers, database transactions, or network connections, or its list of the worker's ports is not empty, or its WorkerGlobalScope is actually a SharedWorkerGlobalScope object (i.e. the worker is a shared worker).

I believe the goal here is to avoid GC'ing orphan workers whose existence can be observed from other contexts.

Should this list somehow include BroadcastChannel? I don't see any reference to it and AFAICT BroadcastChannel doesn't use entanged ports, so its not included that way.

@wanderview
Copy link
Member Author

This would perhaps close one of the observable things mentioned in #2553.

@annevk
Copy link
Member

annevk commented Sep 5, 2018

I think you're correct that it needs to be listed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants