program with:
valgrind --suppressions=libvips.supp --leak-check=yes ./myprogram
And hopefully you'll see "0 bytes definitely lost".
John
On 28 July 2016 at 17:18, Norman Goldstein <norm...@telus.net> wrote:
I'd like to understand how to confirm a potential memory leak in
I'd like to understand how to confirm a potential memory leak in gtk3.
Valgrind shows a definite leak, and "top" shows a steadily increasing
resident set size (RES). However, as I have come to understand, due to
how gtk/glib uses slices for memory management, and how the main loop of
gtk
