On Sun, 2009-06-14 at 10:50 +0100, rob wrote: > Package: xserver-xorg > Version: 1:7.4+3 > Severity: normal > > Note: running Enlightenment E17 built from svn
[...] > ==13275== 40,991,344 (40,747,328 direct, 244,016 indirect) bytes in 40,271 > blocks are definitely lost in loss record 229 of 229 > ==13275== at 0x4C2391E: malloc (vg_replace_malloc.c:207) > ==13275== by 0x4F3505: Xcalloc (in /usr/bin/Xorg) > ==13275== by 0x433BB4: dixAllocatePrivate (in /usr/bin/Xorg) > ==13275== by 0x433C32: dixSetPrivate (in /usr/bin/Xorg) > ==13275== by 0x4CDE48: (within /usr/bin/Xorg) > ==13275== by 0x5321D3: (within /usr/bin/Xorg) > ==13275== by 0x442629: AllocARGBCursor (in /usr/bin/Xorg) > ==13275== by 0x52E83F: (within /usr/bin/Xorg) > ==13275== by 0x44D373: Dispatch (in /usr/bin/Xorg) > ==13275== by 0x43321C: main (in /usr/bin/Xorg) This looks like a smoking gun, but the smoke is hiding the symbols. ;) Can you install xserver-xorg-core-dbg and get another valgrind leak report? http://bugs.freedesktop.org/show_bug.cgi?id=22277 might be related. -- Earthling Michel Dänzer | http://www.vmware.com Libre software enthusiast | Debian, X and DRI developer -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
