Re: [ServiceWorker] Workers & SharedWorkers within ServiceWorkers (#678)

> Of course, even with waitUntil the browser reserves the right to kill the SW if it suspects foul play, such as using push/sync to be performing bitcoin mining or the like.

But I can create 100 background sync service workers that all attach to the same SharedWorker to try to keep it alive so the SharedWorker can do bitcoin mining?  This seems like an uphill battle to me.

It just seems these "heuristics" are going to make a lot of compat issues between browsers and browser version s that will bite developers while still letting people game the system.

Maybe the time has come to be more explicit in the spec about lifecycle of the ServiceWorker?

Or perhaps we should put a CPU throttle on workers without a window.  They are useful for I/O things, but if you try to use them for heavy CPU usage you will run slow.

---
Reply to this email directly or view it on GitHub:
https://github.com/slightlyoff/ServiceWorker/issues/678#issuecomment-95189778