Open dignifiedquire opened 1 year ago
Some teams at Amazon have also encountered segfaults related to FuturesUnordered
; they switched to Tokio's JoinSet
. They've given me a backtrace, but it contains some proprietary symbol names and the like, and I'm not sure how useful it would be. I may anonymize it. It seems superficially similar to the backtraces I see here.
(https://github.com/rust-lang/futures-rs/pull/2809 may or may not have fixed this.)
https://github.com/rust-lang/futures-rs/issues/2863 likely has (not very minimal, but still) reproduction of segfault that may have the same root cause
I think it is likely that 0.3.31, which fixed #2863, also fixed this problem.
We have been debugging spurious issues with segfaults for a while, and while running our code through valgrind tracked some of the issues down to
futures-rs
unfortuantely:The logs we have so far are below:
Reference: https://github.com/n0-computer/iroh/issues/1646