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

RE: Memory leak in SSL binds, OpenLDAP 2.0.23

I should also point out that the authid is correctly freed in the 2.1 code.
particular patches have not been backported to 2.0, so this leak is still
in 2.0.25. If you can, I'd suggest upgrading to 2.1.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support

> -----Original Message-----
> From: Tim Murphy [mailto:tmurphy@micromuse.com]

> Thanks for your very interesting response. I am slowly beginning to
> understand.
> In the particular case I am dealing with, it seems that the sasl context
> is never allocated (don't know why yet) and this means that when
> ldap_int_sasl_external()  tries to add the authid (percolated up from
> ldap_pvt_tls_getpeer() ), there is no context to put it into.  It
> returns an error condition and the temporary pointer to the authid is
> eventually destroyed, thus leading to a leak. The problem with the leak
> is that frequent usage of the library over a prolonged period causes the
> leak to build up to become quite large.
> It is very odd because it only happens for a particular server but I
> suppose I'll find that out why later.  I have finally sorted out the
> debugger so that I am beginning to be able to see what's going on.
> I was also rather confused about why the server's details are going into
> the sasl context!  Thanks for confirming that this is not correct.
>  Anyhow, I'll let you know when I find out what's going on.