[Xcb] Bug#609478: [libxcb1] Memory Leak reported in valgrind

Brian Paterni bpaterni at gmail.com
Sun Jan 9 11:59:34 PST 2011

Package: libxcb1
Version: 1.7-1
Severity: normal

Hello, according to valgrind, there appears to be a memory leak in libxcb.
Here's a relavant error block when I run glxgears through valgrind:

$ valgrind --leak-check=full glxgears
==11308== 124 bytes in 1 blocks are definitely lost in loss record 49 of 81
==11308==    at 0x4C244E8: malloc (vg_replace_malloc.c:236)
==11308==    by 0x7649DC9: get_peer_sock_name (xcb_auth.c:259)
==11308==    by 0x7649E95: _xcb_get_auth_info (xcb_auth.c:302)
==11308==    by 0x7649918: xcb_connect_to_display_with_auth_info
==11308==    by 0x5860749: _XConnectXCB (in /usr/lib/libX11.so.6.3.0)
==11308==    by 0x584895A: XOpenDisplay (in /usr/lib/libX11.so.6.3.0)
==11308==    by 0x402D0C: main (glxgears.c:749)

-- System Information:
Debian Release: 6.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.37+ (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libxcb1 depends on:
ii  libc6                         2.11.2-7
ii  libxau6                       1:1.0.6-1
ii  libxdmcp6                     1:1.1.0-1

More information about the Xcb mailing list