_owner" is eventually freed, how can valgrind miss that? Would
this be a valgrind "bug" or "feature request"?
On 01/08/16 02:00 AM, Emmanuele Bassi wrote:
Hi;
On 30 July 2016 at 20:00, Norman Goldstein wrote:
It seems the debug version is less confusing for valgri
. Run your 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 wrote:
I'd like to understand how to confirm a potential memory leak in gtk3.
Val
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 play
