-
Notifications
You must be signed in to change notification settings - Fork 13.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
Memory leak with 1.0.0-beta.2 on Mac #24856
Comments
Can you pass the extra flags to valgrind? It's possible that this could just be a bunch of false positives |
I don't think this has anything to do with Rust. A noop C program ( |
valgrind dump with extra flags: https://gist.github.com/abhi-bit/94e1f4dd11a227aae24f @sfackler maybe right, I suspect. |
I'm getting a memory leak on OS X with an empty main rust program, but it doesn't seem to be as serious as this one. But I'm not getting any memory leaks with the C example. valgrind dump with extra flags for both examples: https://gist.github.com/CaseyLeask/c8d61ec45c2e146d5c1f |
@CaseyLeask that may be a dupe of #19776 as pthread destructors do not run on process exit |
Sample code used:
Valgrind output from Linux:
Valgrind output from Mac(Yosemite):
Please let me know if you aren't able to replicate this issue, I could pass valgrind output with
--leak-check=full --show-reachable=yes
Rust Version info:
The text was updated successfully, but these errors were encountered: