16179f34cd
The Valgrind tool can give a full accounting of what memory allocations have yet to be free()d when the program exits. It is easier to find actual memory leaks in the code if all non-leaked allocations are elided from that accounting, which is most easily accomplished by free()ing them. The "most" qualifier is there because some allocations are difficult/ impossible to free, as they are internal to libraries like OpenGL and Xft. The best we can hope for is to cover all allocations made by SolveSpace directly. |
||
---|---|---|
.. | ||
freeze.cpp | ||
freeze.h | ||
manifest.xml | ||
resource.rc | ||
w32main.cpp | ||
w32util.cpp |