Memory leaks happens when destroying a GdkWindow
package: libgtk-directfb-2.0-0
severity: serious
tags: upsteam
It was recently found that during a g-i installation the GTK frontend
can easily cause an out of memory error, due to the big amount of memory
allocated at every installation step (nearly 1 MB).
After some investigations with test GTK applications, the problem was
found to be [1] in the way gdk/directfb releases resources when a
gdkwindow is destroyed ( i suspect because of [1] a missing
g_object_unref() somewhere, but that's just my supposition ).
Awaiting now a reply from gtk/dfb maintainers.
CC'ing debian-boot as this strongly impacts on g-i usability.
[1]
http://mail.gnome.org/archives/gtk-devel-list/2006-December/msg00063.html
Attilio Fiandrotti
Reply to: