Re: GTK+ 2.10.10 released

[Emmanuele Bassi <ebassi gmail com>]

On Mon, 2007-03-12 at 18:33 -0700, Sergei Steshenko wrote:
 
> > * Bugs fixed:
> ...
> >  399907	Memory leak in gtk_page_setup dialog
> >  402565	[PATCH]GtkPrintBackendFile leaks string
> ...
> >  403139	Leak reported by valgrind
> 
> ===============================================
> ===============================================
> http://gtk.org/faq/#AEN703 :
> 
> 5.28. Why does GTK+/GLib leak memory?
> 
> It doesn't. 
> ...
> 
> I am still waiting :-).

could you please turn your brain on and *read what's in the FAQ* instead
of playing dumb?

here, let me copy and paste it:

| 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.

you had many developers telling you the meaning of that "it doesn't",
aside from the fact that the FAQ clearly and explicitly writes it in
plain english.

ciao,
 Emmanuele.

-- 
Emmanuele Bassi,  E: ebassi gmail com
W: http://www.emmanuelebassi.net
B: http://log.emmanuelebassi.net