[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#7757) Memory leak



That was quick  !  And my leak is gone.

Thank you
Markus

-----Original Message----- 
From: Howard Chu
Sent: Tuesday, December 03, 2013 10:17 PM
To: huaraz@moeller.plus.com ; openldap-its@openldap.org
Subject: Re: (ITS#7757) Memory leak

huaraz@moeller.plus.com wrote:
> Full_Name:
> Version: 2.4.33
> OS: OpenSuSe 12.3
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (2a01:348:1f9::11)
>
>
> I identified a memory leak when using sasl
>
> ==14039== 34 (32 direct, 2 indirect) bytes in 2 blocks are definitely lost 
> in
> loss record 561 of 666
> ==14039==    at 0x4C2C27B: malloc (in
> /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
> ==14039==    by 0x558E764: ber_memalloc_x (memory.c:228)
> ==14039==    by 0x558A8B7: ber_get_stringal (decode.c:582)
> ==14039==    by 0x558AFF5: ber_scanf (decode.c:806)
> ==14039==    by 0x535535D: ldap_parse_sasl_bind_result (sasl.c:327)
> ==14039==    by 0x5351FE1: ldap_int_sasl_bind (cyrus.c:551)
> ==14039==    by 0x5355810: ldap_sasl_interactive_bind (sasl.c:474)
> ==14039==    by 0x5355A0C: ldap_sasl_interactive_bind_s (sasl.c:511)
> ==14039==    by 0x44DDC9: tool_sasl_bind (ldap.c:2338)

A fix for this is now in git master (rev
f8efeb42783f958dd0dc997f8084e6b3b4502830 )

Please test and report your results, thanks.

-- 
   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/