Valgrind shows memory leak with possibly lost when running tests with cargo test
#141084
Labels
A-valgrind-full-leak
Area: memory leaks detected by valgrind leak-check=full
C-discussion
Category: Discussion or questions that doesn't represent real issues.
T-libs
Relevant to the library team, which will review and decide on the PR/issue.
When running
cargo test
undervalgrind
will full leak check, valgrind shows a memory leak backtrace with "possibly lost" bytes.This happens with the default template code generated by
cargo new
/cargo init
and affects stable rust versions starting from1.86.0
. No memory leak is observed with older1.85.0
.Repro:
I expected to see this happen: No memory leaks reported.
Instead, this happened: Memory leaks reported for
1.86.0
as well as the latest nightly:No memleak with 1.85:
Memleak with 1.86:
Memleak with latest nightly:
Meta
rustc +1.86.0 --version --verbosee
:rustc +nightly --version --verbosee
:The text was updated successfully, but these errors were encountered: