-
Notifications
You must be signed in to change notification settings - Fork 637
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
Node don't stop on Ctrl-C #4242
Comments
Note, although the error indicate "trap is triggered on WebAssembly side" but I haven't figured out why this error message comes from. And, there's no transaction so no wasm runtime execution for a while before press "C-c". But this does related to wasm runtime: if this node has ever execute anything in wasm runtime since node restart and
|
related #3266 |
Huh, apparently wasmer 0.17 used to catch sigint for no good reason? wasmerio/wasmer#1552 This probably will be fixed with the transition to wasmer 1.0 |
Adding that on my machine there's a similar, but slightly different behavior: the first Ctrl+C does say it's gracefully exiting with Machine:
|
Duplicate of #3266 |
On first Ctrl-C it has no effect, node continues to run. On second Ctrl-C, it says:
Full log:
The text was updated successfully, but these errors were encountered: