Fix memory leaks in OpenWalnut
The workflow for the logs is the workflow described in #486 (closed)
definitely-lost.txt => No pointer to block could be found (23 entries)
indirectly-lost.txt => The block is not lost, but the pointers that point to the blocks are lost (2612 entries)
possibly-lost.txt => One pointer may be an interior pointer (1357 entries)
The still reachable log won't be added here, as those are not really of interest (220366)
The nodejs script to seperate the logs: index.js
valgrind options used:
valgrind --leak-check=full
--show-leak-kinds=all
--track-origins=yes
--verbose
--log-file=valgrind-out.txt
bin/openwalnut-qt