Open roblatham00 opened 3 years ago
Thanks for the report, @roblatham00 .
We just merged a PR from @rgmiller to fix a bunch of memory leaks that he also identified with valgrind: https://github.com/LLNL/UnifyFS/pull/684
Were you using a build after this PR was merged?
I'm using a build from today 178dfd5b71 . I did notice commit 9058fe7 (which got me thinking you're in the mood for memory leak bug reports) but those are all server side changes.
System information
Describe the problem you're observing
Merely initializing and finalizing unify causes memory sanitizers (valgrind, address sanitizer) to report memory leaks
Describe how to reproduce the problem
valgrind --leak-check=full --show-reachable=yes
will uncover leaked memory as will compiling with-fsanitize=address
Include any warning or errors or releveant debugging data
This simple routine initializes and finalizes unify
and when compiled with
-fsanitized=address
, I get the following leaks in the unify configuratorpriority: low -- 223 bytes is a trivial amount of memory. they are more annoyances when I'm trying to find my own memory leaks