-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Valgrind reports multiple memory leaks, when checking random folders with red_knot #14945
Comments
Can you try commenting out this line ruff/crates/red_knot/src/main.rs Line 216 in 81e5830
We intentionally "leak" the Database right before shutting down the CLI because it's expensive to deallocate and we know that the process is going to end in a few ms anyway. |
When I compile red_knot locally, then I see in valgrind such error (rui314/mold#1240)
so in valgrind I see now only this leaks, which looks a little like false positives
|
I'm not super experienced reading valgrind output, but the remaining issues don't look like anything addressable in red-knot. Are we satisfied that the only real leak is the known and intentional (I'm going to hazard a guess on "yes" and go ahead and optimistically close this, but feel free to comment if you think it should be re-opened and I'll happily do so.) |
ruff 0.8.2+1582 (45b565c 2024-12-12)
When testing with red_knot(
valgrind --leak-check=full red_knot_normal --current-directory .
) random directories, I see in valgrind such memory leaksPrecompiled binary with debug symbols, updated daily - https://github.com/qarmin/Automated-Fuzzer/releases/download/Nightly/red_knot_normal.7z
The text was updated successfully, but these errors were encountered: