-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Valgrind reports a leak of 32 Bytes for a std::thread. #71616
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Maybe updating to latest valgrind (3.15) helps. |
I just compiled a 3.15 version of valgrind and it did not make any change :/ |
Cannot reproduce. I have llvm-10, valgrind-3.15, rustc 1.44.0-nightly (b2e36e6 2020-04-22) |
Hm, my guess is that this is not reproducible on systems that do have __pthread_get_minstack -- but if you don't, then calling dlsym will return an error which isn't cleared -- indeed, I can't see an API to do so. Presumably that's the cause of the "bug" here. AFAICT, we can't do anything about the leak anyway -- there's no API to clear the error. With that in mind, I'm going to close since it seems like we can't do anything about this. |
I tried this code:
The code compiles and Hello, world! gets printed as expected but valgrind reports a leak of still reachable 32 Bytes:
Meta
rustc --version --verbose
:Backtrace
The text was updated successfully, but these errors were encountered: