WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED INVALID
22727
Consider implementing "kill a worker" algorithm for politely closing Workers
https://bugs.webkit.org/show_bug.cgi?id=22727
Summary
Consider implementing "kill a worker" algorithm for politely closing Workers
Alexey Proskuryakov
Reported
2008-12-07 03:48:36 PST
The Web Workers draft spec has a mechanism for politely closing Workers, sending them an onclose event to clean up. It doesn't say when it is invoked, though presumably that's each time a Worker object is destroyed, except for those already terminated explicitly. Being able to clean up after execution seems useful, we should consider implementing this.
Attachments
Add attachment
proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1
2008-12-07 04:01:04 PST
<
rdar://problem/6425819
>
Ahmad Saleem
Comment 2
2022-08-11 10:36:17 PDT
Safari / Webkit does not support nested workers but pass all other WPT tests related Workers close:
https://wpt.fyi/results/workers?label=master&label=experimental&aligned&view=subtest&q=worker%20close
ap@webkit.org
- Is this needed any more or we can close this? Thanks!
Alexey Proskuryakov
Comment 3
2022-08-19 18:40:54 PDT
This would be applicable to regular web workers too, not just nested workers. I haven't been following spec changes, but there isn't any "kill a worker" algorithm at <
https://html.spec.whatwg.org/multipage/workers.html#workers
>, and "close a worker" doesn't dispatch events. So looks like this doesn't exist any more.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug