You need to set the malloc routines to use the real system malloc;
export G_DEBUG=gc-friendly
export G_SLICE=always-malloc
I have this suppressions file:
https://github.com/jcupitt/libvips/blob/master/libvips.supp
That's for a gobject-based library, you might need to add a few things
to it. 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 <norm...@telus.net> wrote:
> 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
> plays a part, things are not as straightforward as I have just outlined. Is
> there a definitive guide, "How to confirm a memory leak in GTK"? I have
> only seen various relevant pages on the net.
> _______________________________________________
> gtk-app-devel-list mailing list
> gtk-app-devel-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
_______________________________________________
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
