How to confirm a memory leak

2016-07-30 Thread Norman Goldstein
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

Re: How to confirm a memory leak

2016-07-30 Thread jcupitt
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 ad