On Thu, 11 Mar 2010 08:08:51 +0100 Friedrich Dominicus <frido@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > Vikram Noel Ambrose <noel.ambrose@xxxxxxxxx> writes: > > > > > I just suppress everything not coming out of my source files and > > leave it at that. GTK is not something any single person could go > > through and find all the memory leaks. > IMHO that should have been always high on the priority list of the gtk > developers. Howerver how long do the "typical" applications run? Are > there very long running GTK applications around? It would be nice if someone in the gtk+/gnome projects were to produce a suppression file (there was work on one for gtk+-2.12) but the motivational problem is that there aren't any significant memory leaks in gtk+ (as opposed to program-duration memory allocation which is not taken down on termination). The library user can go some way to making her own by starting simple programs which are known not to leak which allocate the objects of interest in her program, together with requiring glib memory allocation to use g_malloc() when testing and producing the suppressions, rather than slices. There are some long lasting gtk+ applications, including in particular gnome itself. I sometimes have it up weeks at a time on my laptop, where I tend to suspend rather than close down. Chris _______________________________________________ gtk-list mailing list gtk-list@xxxxxxxxx http://mail.gnome.org/mailman/listinfo/gtk-list
