-
Notifications
You must be signed in to change notification settings - Fork 68
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
Light Web Node panic after restart #3101
Comments
Duplicate of #2875, although in NodeJS this is an "Uncaught exception" and exits the process if not handled in userland. |
Strack traces for both panics, and one additional one that I see alongside it:
|
If I understand it correctly, Rust panics in wasm do not trigger stack unwinding, so destructors aren't called. This means one shouldn't call into a wasm blob after it has panicked. The Thus, I think, it makes sense to focus on the other panics. Unfortunately, the // if the receiver was dropped we do nothing.
tx.send(()).unwrap_throw(); |
That code is from line 72, though. Line 104 is this code: 103 fn poll(mut self: Pin<&mut Self>, cx: &mut Context) -> Poll<Self::Output> {
104 Future::poll(Pin::new(&mut self.rx), cx).map(|t| t.unwrap_throw())
105 } |
Yes, it's the same code, but without the comment. Digging deeper, it was introduced by rustwasm/gloo#98 (comment) (similar comment on the one with the suspicious code comment: rustwasm/gloo#98 (comment)). We're in the I'm again confused and not sure where to continue. |
Happens after restarting the node (killing the app and starting it again)
Env:
The text was updated successfully, but these errors were encountered: