[Xcb] mem leak with ecore_xcb

Barton C Massey bart at cs.pdx.edu
Wed Apr 11 08:32:50 PDT 2007

In message <Pine.LNX.4.64.0704111140420.26273 at grozny.maths.univ-evry.fr> you wrote:
> After having found a nasty bug, ecore_xcb behaves well. Nevertheless, when 
> running a test through valgrind, I have those 2 messages when the prog 
> shuts down:
> ==31763== 24 bytes in 1 blocks are still reachable in loss record 2 of 3
> ==31763==    at 0x401A6F0: malloc (vg_replace_malloc.c:149)
> ==31763==    by 0x4494E6C: XauFileName (AuFileName.c:67)

I committed a fix to this one a little while back, in the
case where XauFileName() is called from inside libXau().
Make sure you have the latest XCB: if it still shows the
problem, please set a breakpoint in XauFileName and get me a
stack backtrace...


> ==31763==
> ==31763== 936 bytes in 26 blocks are definitely lost in loss record 3 of 3
> ==31763==    at 0x401A6F0: malloc (vg_replace_malloc.c:149)
> ==31763==    by 0x42864D5: read_packet (xcb_in.c:144)

Don't know about this one.  Jamey can fix, if he ever gets
his email caught up.  Otherwise bug me in a week or so and
I'll poke at it.


More information about the Xcb mailing list