From alinachegalati@yahoo.com Wed Jan 27 16:48:15 2010
From: alinachegalati@yahoo.com
To: openldap-bugs@openldap.org
Subject: Re: (ITS#6453) OpenLDAP memory leak on LDAP_TIMEOUT
Date: Wed, 27 Jan 2010 16:48:15 +0000
Message-ID: <201001271648.o0RGmFnH089522@boole.openldap.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============7794411742157338647=="
--===============7794411742157338647==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
--0-1999948331-1264610847=3D:54320
Content-Type: text/plain; charset=3Dus-ascii
We found out that this call :
ldap_msgfree(res);
does not get executed because the LDAPMessage is NULL (res is null) in case t=
he timeout is on the client side.
There is any other way to clean it?
=20
--0-1999948331-1264610847=3D:54320
Content-Type: text/html; charset=3Dus-ascii
We found out that this call :
ldap_msgfree=
(res);
does not get executed because the LDAPMessage is NULL (res is n=
ull) in case the timeout is on the client side.