Re: Re[2]: Does GTK leak memory

[Emmanuele Bassi <ebassi gmail com>]

On Wed, 2010-06-02 at 15:36 +0200, Lothar Scholz wrote:
> Hello Emmanuele,
> 
> EB> "leaks" how? some internal objects are singletons, and won't be freed
> EB> for the entire duration of the application's lifetime.
> 
> A good libary/toolkit should always free singletons inside an exit
> handler.

that's opinable.

personally, no: I don't think it's at all necessary. and I've been doing
memory profiling of glib- and non-glib based libraries and applications
for a while.

you are, of course, free to start asking people to use atexit() handlers
to free up one-off allocations, starting from the bottom of the stack
(font-config, freetype, X11, glibc, Mesa, etc.) and moving up towards
gtk+.

> Just for the reason that using memory debugging tools is confusing
> if it is not doing it.

you can use suppression files to mask the known one-off allocations.

ciao,
 Emmanuele.

-- 
W: http://www.emmanuelebassi.name
B: http://blogs.gnome.org/ebassi