Attilio Fiandrotti wrote:
Hi
I recently noticed the the size of a generic gtk/dfb application
considerably grows over time while the same application, but compiled
for gtk/x11, does not.
The attached example aplication permanently sets up a window and an
external box and at every proram's
2006/12/18, Attilio Fiandrotti [EMAIL PROTECTED]:
Attilio Fiandrotti wrote:
Hi
I recently noticed the the size of a generic gtk/dfb application
considerably grows over time while the same application, but compiled
for gtk/x11, does not.
The attached example aplication permanently
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
Kalle Vahlman wrote:
2006/12/18, Attilio Fiandrotti [EMAIL PROTECTED]:
Attilio Fiandrotti wrote:
Hi
I recently noticed the the size of a generic gtk/dfb application
considerably grows over time while the same application, but compiled
for gtk/x11, does not.
The attached example
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
Okay I know about this a bit.
Obviously a logic error exists and I've not figured out the right answer yet.
The reason Destroy is commented out is we should never need to call
it on the gdk side.
The problem was related to the need to keep the DirectFB window alive
long enough to
clear out the
Hi
I recently noticed the the size of a generic gtk/dfb application
considerably grows over time while the same application, but compiled
for gtk/x11, does not.
The attached example aplication permanently sets up a window and an
external box and at every proram's iteration a textview is
