Closed matu3ba closed 2 years ago
At least the memory leak size etc is consistent, so havoc
does only forget to clean up some permanently needed resources on closing.
Havoc uses libraries that might rely on the OS to do some cleanup, looks like libxkeyboard and libffi(used by wayland lib) do that. I'll have a look later anyway though, just in case.
Yea, there are no memory leaks here. You can see in the summary it always says lost: 0 bytes in 0 blocks
.
These are just bits of memory not cleaned up before the program exits, but they're still reachable and not growing with time.
I added a commit to fix one of these to make the valgrind output smaller, the rest are in the wayland and xkbcommon libraries though I think.
Running in shell
valgrind -s --leak-check=full --show-leak-kinds=all ./havoc &> leak_report.txt
and closing the terminal leads to the following report: