-
Notifications
You must be signed in to change notification settings - Fork 653
Panic - Future still here when dropping #2278
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
Comments
The last line seems pretty interesting:
|
Could you provide code to reproduce this issue?
Double panic will be converted to abort. By using this mechanism, you can use the same functionality as unstable |
Unfortunately I can't provide code to reproduce this. This was reported by one of our users. The backtrace wasn't sufficient to isolate the exact code path and I've not seen this occur before apart from this. :( |
Hi, I also experience this strange crash and I'm kind of lost. This is the stripped down code I use to reproduce the behaviour: If I run the executable and then plug an USB joystick into my machine (which causes the
I did not try to reproduce this without the stick crate (and therefore without hardware dependency), yet. |
This has since been resolved |
Any reference to where this was fixed? I also am experiencing this issue and using nightly. The error seems to happen very sporadically, so it is extremely hard to reproduce. For completeness here's my stack trace:
host: Thanks! |
Hey all,
A user has experienced a panic. The exact state of the application is not known, however it appears there is an unexpected panic in the
FuturesUnordered
struct. It appears they are hitting this "bomb"futures-rs/futures-util/src/stream/futures_unordered/task.rs
Lines 109 to 111 in 1fa794a
Here is the provided backtrace
The text was updated successfully, but these errors were encountered: