-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Panic at linked_list.rs - reborn #6597
Comments
What dependencies are you using? |
Hi, attached the full Cargo tree. |
Sorry I don't think there's enough information here for us to do anything. |
What else do you think could help? Would having the core dump do? |
Sorry, I have no idea what to look for in a core dump. |
This panic may hit #6612 |
For what it's worth, this is what I'm able to extract from the core file:
BTW what I'm naively trying to do here is implement my own timeout into a |
That crate has a lot of unsafe code, a lot of yanked versions, and no public repository, so I'm not feeling so confident about it. Incorrect unsafe code in a third-party crate can easily lead to the error you are seeing, so based on that, that would be my first theory. |
Yes I had a feeling too that this may be the root cause. I'm going to see if I can avoid using it. Thanks! |
I'm no expert on pin/unpin magic but I think it's caused by https://github.com/StoicDeveloper/mapped_futures/blob/master/src/mapped_futures/mod.rs#L288 which inadvertently moves futures even if they're |
I'm considering at the moment replacing Mapped Futures with the more standard StreamMap. Aren't these crates basically doing the same thing? Sorry if I'm misunderstanding something, this whole Future mechanism is getting me quite a bit confused. Also if someone has an idea how to have a timeout when doing the |
I'm going to close this because it is a bug in a third-party library. You can add a timeout to let Ok(value) = timeout(max_dur, my_stream.next()).await else {
// handle timeout
}; For further help, please ask on our Discord server or open a discussion. |
FWIW I'm experiencing the same panic and I don't think it's coming from a third-party library |
@bnjjj Please open a new issue. Please include an explanation of why it is unlikely to be in a third-party library. |
Version
Platform
Description
I seem to be able to reproduce the bug mentioned in #5782.
Error message:
The stacktrace looks like this:
I can provide privately if helpful the binary that produced the crash, the associated core dump and the session logs.
Works on my MacOS Monterey 12.7.5 with
The text was updated successfully, but these errors were encountered: