-
Notifications
You must be signed in to change notification settings - Fork 170
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
iroh-net: valgrind error: invalid atomic reads #1646
Comments
dignifiedquire
added a commit
that referenced
this issue
Oct 16, 2023
Workaround for #1646 and likely makes more sense in the context of Tokio usage anyway. In general `JoinSet` is simply used instead.
This was referenced Oct 16, 2023
github-merge-queue bot
pushed a commit
that referenced
this issue
Oct 17, 2023
## Description Workaround for #1646 and likely makes more sense in the context of Tokio usage anyway. In general `JoinSet` is simply used instead.
Fixed in #1647 |
dignifiedquire
added a commit
that referenced
this issue
Oct 18, 2023
## Description Workaround for #1646 and likely makes more sense in the context of Tokio usage anyway. In general `JoinSet` is simply used instead.
3 tasks
matheus23
pushed a commit
that referenced
this issue
Nov 14, 2024
## Description Workaround for #1646 and likely makes more sense in the context of Tokio usage anyway. In general `JoinSet` is simply used instead.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This looks like an issue in https://github.com/rust-lang/futures-rs/blob/master/futures-util/src/stream/futures_unordered/ready_to_run_queue.rs and more specifically in the way
drop
is implemented.This might or might not be responsible for the
malloc
crashes we have been seeing in CIThe text was updated successfully, but these errors were encountered: