Bug 19978 - Memory leak on a failed connection attempt.
Memory leak on a failed connection attempt.
Status: CLOSED ERRATA
Product: Red Hat Linux
Classification: Retired
Component: openldap (Show other bugs)
7.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
Aaron Brown
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-10-29 01:43 EST by Sam Varshavchik
Modified: 2007-04-18 12:29 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-06-04 18:19:33 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Sam Varshavchik 2000-10-29 01:43:05 EST
If the LDAP server is down, the failed connection attempt appears to leak
memory.  Example program:


#include <lber.h>
#include <ldap.h>

int main()
{
	LDAP *p;

	for (;;)
	{
		p=ldap_init("127.0.0.1", 389);

		if (!p) break;

		printf("%d\n",
		       ldap_simple_bind_s(p, "dc=example.com",
					  "foobar"));
		printf("unbind=%d\n",
		       ldap_unbind_s(p));
	}
	return (0);
}


If the server is down, this leaks memory rather quickly.  If the server is
up, but binddn/bindpw is wrong, there is no memory leak.  If the server is
up, and binddn and bindpw is right, no memory leak.  Only when there's a
failure to establish a connection
Comment 1 Sam Varshavchik 2001-04-28 18:44:53 EDT
Reconfirmed with openldap 2.0.7

Kicked upstream. http://www.openldap.org/its/index.cgi?findid=1116
Comment 2 John Morrissey 2002-04-21 15:49:37 EDT
This has been fixed upstream in 2.0.19. The RH errata release 2.0.21-1 picks up
this fix.

This bug should be marked as resolved.
Comment 3 Daniel Roesen 2005-06-04 18:19:33 EDT
After three years, doing so now. :-)

Note You need to log in before you can comment on or make changes to this bug.