Re: Why do a gtk/directfb process grows bigger and bigger ?
- From: Attilio Fiandrotti <attilio fiandrotti gmail com>
- To: gtk-devel-list gnome org
- Subject: Re: Why do a gtk/directfb process grows bigger and bigger ?
- Date: Mon, 18 Dec 2006 16:13:37 +0100
Loïc Minier wrote:
On Mon, Dec 18, 2006, Attilio Fiandrotti wrote:
so, i guess this patch only tackles the issue but does not properly.
Attilio, did you notice the following block near the end of
_gdk_windowing_window_destroy which your patch touches:
#if 0 /* let the finalizer kill it */
if (!recursing && !foreign_destroy)
impl->window = NULL;
There's no other call to Destroy() in this file, so perhaps the
Destroy() call is never made. Could you try without the #if 0 instead
of your patch?
That was the first thing i tried, but i got a crash :(
Also, did you valgrind your test case? It should immediately point at
the place where memory is leaked from I suppose.
I suspect we're not actually leaking (in the sense of not freeing
something), but rather not unreferencing something somewhere after
disallocation: i really hope mike or sven can fix this :)
] [Thread Prev