Re: Problem with memory leaks in Glade and GLADE

["Jeff C," <nolongersafeto@userealemailsniff.com>]

"Dr. Adrian Wrigley" <amtw@linuxchip.demon.co.uk.uk.uk> wrote in message
news:R15cb.2820$jJ3.43467@newsfep4-glfd.server.ntli.net...
> Stephen Leake wrote:
> > Yes. The GtkAda list is quite helpful. See
> > http://libre.act-europe.fr/GtkAda/ for info on how to subscribe (in
> > the Authors section).
>
> OK.  I've been looking at the list.  Useful to keep in touch with.
>
> Unfortunately (?) I have found the leak problems are mirrored in the
> C version of the demo code "gtk-demo".  This code also sucks in RAM each
time
> the pointed enters the main selection window, (as well as taking in
> a megabyte or two extra each time a function is activated).


Not sure this is applicable but I remembered seeing something about the glib
free routines

http://docs.linux.cz/gtk-faq/x672.html

Why does GTK+/GLib leak memory?
It doesn't. Both GLib and the C library (malloc implementation) will cache
allocated memory on occasion, even if you free it with free().

So you can't generally use tools such as top to see if you are using free()
properly (aside from the very roughest of estimations, i.e. if you are
really, really screwing up top will show that, but you can't distinguish
small mistakes from the GLib/malloc caches).

In order to find memory leaks, use proper memory profiling tools.