I think the "Web Worker has gone away" #bug in #WebKit is back (possibly only for installed web apps of course).
I do use the workaround where I keep a ref to the worker (window._worker = new Worker(...)) but that doesn't seem to solve the issue. Just ran into it, attached dev tools, switched to worker context, tried console.log('hi!') and nothing happened (dev tools refused to send the command, even).
In the page context, window._worker reports the worker is there and { terminated: false }
The bug doesn't happen as long as you have dev tools attached, of course. And sometimes (most of the time?) it just keeps working. And then it suddenly doesn't.
@jaffathecake @surma any idea and/or tips on how to debug this so I can file a ticket?
Right might as well ask some webkit folks too 🤦
(i thought of jake and surma because they talked about worker bug in one of their http203 episodes and I use surma's comlink)
So same question(s) for @othermaciej @bradeeoh :
Any idea and/or tips on how to debug this so I can file a ticket?
@rgadellaa @bradeeoh Do you have a reproducible case? (Doesn’t have to be minimized.) If so, file a bug at https://bugs.WebKit.org and post here. If it reproduces on one device but not others, then it would be helpful if you could file via Feedback Assistant with full logs.
Yeah I was trying to build a simplified testcase but that worker just keeps running as expected. But in the full web app it gets killed pretty consistently. Will check Feedback Assistant (never used that, have to look it up) & report back. Thanks!
@rgadellaa @bradeeoh We have automated testing of Web Workers, and many sites rely on them, so we don’t think they are _always_ going away. That’s why a repro case would be helpful.