Bug 179395
| Summary: | [Service Worker] Termination policy | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Joseph Pecoraro <joepeck> |
| Component: | WebKit Misc. | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | beidson, cdumez, ggaren, joepeck, olivier, webkit-bug-importer, youennf |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=174541 | ||
Joseph Pecoraro
[Service Worker] Termination policy
Service workers don't always get terminated as one would expect.
Steps to Reproduce:
1. Load <https://mdn.github.io/sw-test/>
2. Navigate to <https://webkit.org>
=> Service Workers <https://mdn.github.io/sw-test/sw.js> is still alive
Relatedly, currently just reloading a page with a service worker causes a new service worker to spawn:
Steps to Reproduce:
1. Load <https://mdn.github.io/sw-test/>
2. Reload 3 times
=> Multiple Service Workers exist for <https://mdn.github.io/sw-test/sw.js>
Both cases can result in a large list of Service Workers show up as inspector debug targets, and when there are duplicates it is unclear which is the active worker.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/35398704>
Joseph Pecoraro
When a Service Worker has a debugger/inspector attached we should consider not terminating it until the debugger/inspector has disconnected.
Brady Eidson
Yup, we never terminate. It's an algorithm we need to implement and then use, obviously.
I'll be stubbing out in: https://bugs.webkit.org/show_bug.cgi?id=179401
Geoffrey Garen
*** This bug has been marked as a duplicate of bug 179401 ***