XOpenDisplay() lags memory? (valgrind)

Christian Parpart trapni at gentoo.org
Thu Feb 22 12:00:43 PST 2007

Hi all,

I'm cleaning up a little, so I valgrind'ed, and this is one that's left:

==24707== 25 bytes in 1 blocks are still reachable in loss record 2 of 3
==24707==    at 0x4A20CFB: malloc 
(in /usr/lib64/valgrind/amd64-linux/vgpreload_memcheck.so)
==24707==    by 0x510BFD6: XauFileName (in /usr/lib64/libXau.so.6.0.0)
==24707==    by 0x510C212: XauGetBestAuthByAddr 
(in /usr/lib64/libXau.so.6.0.0)
==24707==    by 0x4F50598: _X11TransConnectDisplay 
(in /usr/lib64/libX11.so.6.2.0)
==24707==    by 0x4F37455: XOpenDisplay (in /usr/lib64/libX11.so.6.2.0)
==24707==    by 0x401539: main (encode-stream.cpp:88)

However, I definitely did call XCloseDisplay(dpy) at the end, that's why I 
feel so confusing.

Is this a bug, or could I have been missing something?

Thanks in advance,
Christian Parpart.

p.s.: Xorg 7.2
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.x.org/archives/xorg/attachments/20070222/f2450672/attachment.pgp>

More information about the xorg mailing list