Comment 36 for bug 328232

Revision history for this message
In , Shuang-he (shuang-he) wrote :

Ok, I have caught following leak on aspire one with KMS/UXA/DRI2/compiz, it just means 326 bo are lost in composite extension (the '0 bytes' is some trick I used with valgrind to catch such memory leak):

==14839== 0 bytes in 326 blocks are definitely lost in loss record 1 of 124
==14839== at 0x55AA62F: drm_intel_gem_bo_alloc_internal (intel_bufmgr_gem.c:4 28)
==14839== by 0x55A61C3: drm_intel_bo_alloc_for_render (intel_bufmgr.c:58)
==14839== by 0x55608B6: i830_uxa_create_pixmap (i830_exa.c:976)
==14839== by 0x8138E3B: compNewPixmap (compalloc.c:478)
==14839== by 0x81392D4: compAllocPixmap (compalloc.c:556)
==14839== by 0x8138939: compCheckRedirect (compwindow.c:161)
==14839== by 0x8138A2F: compRealizeWindow (compwindow.c:242)
==14839== by 0x806F9EB: RealizeTree (window.c:2605)
==14839== by 0x807179A: MapWindow (window.c:2698)
==14839== by 0x8139A9D: compRedirectWindow (compalloc.c:179)
==14839== by 0x8139D6C: compRedirectSubwindows (compalloc.c:320)
==14839== by 0x81368C1: ProcCompositeRedirectSubwindows (compext.c:172)