New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VM: Implement Isolate.kill #21189
Comments
Marked this as blocking #21599. |
Added this to the 1.9 milestone. |
Issue #21053 has been merged into this issue. |
With https://codereview.chromium.org/800713002 I can run: import "dart:isolate"; isolateMain(loopForever) { printUsage() { main(args) { // Spawn the isolate. // Keep pinging the isolate. Only exit if the isolate stops responding Set owner to @iposva-google. |
Sounds good. We also need to deal with all the external resources an isolate has allocated, e.g. open file descriptors. Also something comes back to me regarding the native isolate and handling of responses to outstanding operations which completed for an isolate which is now killed. At some point we talked about a queue for handling these messages, so that the operation can be "undone" to avoid resource leak. If open file completed the file must be closed |
Fixed in r42355 Re: comment 5: Messages originating from C code can contain a redirection port, so the IO code just needs to hook into this API. Added Fixed label. |
Marked this as blocking #22067. |
Make it possible to shut down an isolate by calling Isolate.kill.
The text was updated successfully, but these errors were encountered: