GNOME Bugzilla – Bug 50214
Xft support does not clean up correctly.
Last modified: 2011-02-04 16:09:32 UTC
Frequently when exiting the Xft render support for GNOME dies with an X error. The problem here is that XftDraw is being called (which calls XRenderFreePicture) after the accompanying drawable has been destroyed. But the picture has already been destroyed, so it dies with BadPicture. Simply trapping X errors over this is the quick fix, but a horrible HACK. The right fix is to: - Move the picture into the drawable - Stop using XftDraw, it doesn't buy us anything - Don't free the picture if it has already been freed.
Put all GTK 1.3.x bugs on 2.0.0 milestone
Hi Owen, does this look like an incarnation of this problem or do you think it's a different matter? Steps to reproduce: 1. Fire up testgtk with GDK_USE_XFT set to 1 2. Click on font selection 3. Choose a font and click OK 4. Click on font selection again -> BOOM I bumped the severity to MAJOR because this is a serious problem making the use of antialiased fonts almost impossible. BTW: Are some of the y values ok to look so funny?
+ Trace 9566
Mon Nov 5 12:46:44 2001 Owen Taylor <otaylor@redhat.com> * gdk/x11/gdkdrawable-x11.[ch] gdk/x11/gdkgc-x11.c gdk/x11/gdkpixmap-x11.c gdk/x11/gdkprivate-x11.h gdk/x11/gdkwindow-x11.c: Redo Xft support to go directly to Picture objects instead of using XftDraw. This fixes the problem where we weren't able to properly destroy XftDraw objects before destroying the accompanying windows, and probably improves efficiency a bit too. (#50214)