https://bugs.openldap.org/show_bug.cgi?id=9432
--- Comment #2 from Howard Chu hyc@openldap.org --- (In reply to sternenseemann from comment #0)
Also note that if I don't call sasl_client_done() and link specifically againt cyrus sasl for that purpose, as I never call any sasl related functions, the executable leaks over 20K. It seems like an oversight to me that ldap_unbind_ext doesn't free anything SASL related.
That's because sasl_client_done() deinitializes the entire library, whereas ldap_unbind_ext is only for closing a single session. Since the allocations done by sasl_client_init() only occur once in the lifetime of a process, this isn't actually a significant leak. It would only be significant if it leaked every time a new session was created within the same process.
This ITS is invalid.