Valgrind seems to think that the server leaks in PictureDestroyWindow. It seems like this happens when the server looks up a non-existent private during window destruction. ==3846== 1,505,832 (51,808 direct, 1,454,024 indirect) bytes in 203 blocks are definitely lost in loss record 130 of 145 ==3846== at 0x4A0867E: malloc (vg_replace_malloc.c:207) ==3846== by 0x4F6715: Xalloc (utils.c:1303) ==3846== by 0x4F6A55: Xcalloc (utils.c:1344) ==3846== by 0x43464F: dixAllocatePrivate (privates.c:109) ==3846== by 0x43478C: dixLookupPrivate (privates.c:140) ==3846== by 0x520063: PictureDestroyWindow (picture.c:62) ==3846== by 0x5324E9: damageDestroyWindow (damage.c:1721) ==3846== by 0x56707E5: DRIDestroyWindow (dri.c:1891) ==3846== by 0x525A90C: XvDestroyWindow (xvmain.c:434) ==3846== by 0x47A707: xf86XVDestroyWindow (xf86xv.c:1033) ==3846== by 0x5043049: DbeDestroyWindow (dbe.c:1568) ==3846== by 0x5021BB: compDestroyWindow (compwindow.c:640)
Please refer to bug #16509 for a potential patch.
*** This bug has been marked as a duplicate of bug 16509 ***
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.