You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's hard to even define what is an mmap leak, because mmap-ed data doesn't really ever leak - you can still find all the mappings in /proc/maps and unmap what you don't need, even if all pointers to that mapping are lost.
It should be possible to extend lsan to do the following:
scan all memory to find all pointers to all currently mmap-ed regions (lsan does the full scan anyway).
report mappings that no pointers are pointing to
I don't know how useful such tool is going to be.
(And we are not planing this work)
Hello, thank you for this project
While I'm using LSan I found that it doesn't detect leaks with mmap
Is there any reason why ?
It must be great if someone let me know !
test code is simple like below
The text was updated successfully, but these errors were encountered: