Any ideas why this memory leak is not being detected by valgrind?
Because it's not really possible to do so. Consider the problem of knowing
when an mmap-d page is no longer in use. Those pages are presumably managed
by your app, in some way that is unknown to Valgrind/Memcheck, hence it ha
I think I found the problem. It seems valgrind doesn't detect memory leaks
related to mmap. Why is this the case?
A memory leak is a block that is allocated by
malloc/calloc/realloc/reallocarray,
not yet free()d, and with no in-process pointers to it.
mmap is not malloc, and the result of mmap
I think I found the problem. It seems valgrind doesn't detect memory leaks
related to mmap. Why is this the case?
On Thu, Jan 6, 2022 at 7:30 PM James Read wrote:
> I have a program that definitely has a memory leak. I can see the memory
> usage of the program going up rapidly with htop until it
I have a program that definitely has a memory leak. I can see the memory
usage of the program going up rapidly with htop until it gets killed for
consuming too much memory. Yet this is the output from sudo valgrind -v
--tool=memcheck --leak-check=full --show-reachable=yes --track-origins=yes
--log-
