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)
> {
> if (impl->window)
> impl->window->Destroy (impl->window);
> impl->window = NULL;
> }
> #endif
>
> 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 :)
cheers
Attilio
_______________________________________________
gtk-devel-list mailing list
gtk-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-devel-list
