Re: [w3c/ServiceWorker] postMessage keeps service workers alive indefinitely (#980)

Hah, I just posted the exact same thing @jakearchibald described in the chromium bug for the same issue with regard to foreign fetch ([crbug.com/662443](https://bugs.chromium.org/p/chromium/issues/detail?id=662443)). So yes, I think the solution jake describes makes a lot of sense, when generalized a bit more to apply to any event triggered by another service worker (such as in this case foreign fetch).

Also if in the future we start allowing service workers to start shared and/or dedicated workers, we should make sure that messages/fetches (regular and foreign) made by those workers get the same timeout treatment if a service worker is the only thing holding the worker alive.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/980#issuecomment-259261219