Valgrind reports this leak: ==9349== 504 bytes in 3 blocks are definitely lost in loss record 153 of 223 ==9349== at 0x3414E222: malloc (vg_replace_malloc.c:130) ==9349== by 0x34D09356: XcursorCursorsCreate (cursor.c:34) ==9349== by 0x34D0A5C1: XcursorImagesLoadCursors (cursor.c:671) ==9349== by 0x34D0A6C5: XcursorImagesLoadCursor (cursor.c:697) ==9349== by 0x34D0D4B8: XcursorTryShapeCursor (xlib.c:104) ==9349== by 0x34AD76: XCreateGlyphCursor (in /usr/X11R6/lib/libX11.so.6.2) ==9349== by 0x34B1F2: XCreateFontCursor (in /usr/X11R6/lib/libX11.so.6.2) ==9349== by 0x347D9A71: gdk_cursor_new_for_display (gdkcursor-x11.c:124) ==9349== by 0x347BED9E: gdk_cursor_new (gdkcursor.c:99) ==9349== by 0x80802AB: nautilus_spatial_window_realize (nautilus-spatial-window.c:186)
It just struck me that the leak is probably outside of libXcursor and in xlibs proper? Moving it there.
This looks like a duplicate of bug 1043 maybe?
Compiled a new libXcursor with the fix in bug #1043 and it's gone now. *** This bug has been marked as a duplicate of 1043 ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.