195087 - Memory leak on AIX 5.1 when Bind to host fails

Status: RESOLVED INCOMPLETE

(Directory Graveyard :: LDAP C SDK, defect)

Description

[edward.moraski]

User-Agent:       Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)
Build Identifier: We are using 5.08 LDAP SDK C downloaded from SUN site

We encounter memory leak when bind to host fails on AIX. The same functionality 
works fine on SUN, HP and WIN32.
The leak occurs when the bind attempt fails.  It occurs both in SSL mode and in 
non-SSL mode. 
In the case where SSL is used, the following functions are called in a loop: 

ldapssl_client_init 
ldapssl_init            //pass a bad host name 
ldap_simple_bind  //this call fails 

In non-SSL mode, the following functions are called in a loop: 

ldap_init                //pass a bad host name 
ldap_simple_bind  //this call fails 

In both cases, we observe a memory leak. 

The leak also occurs when the synchronous function ldap_simple_bind_s is used. 

We tested on AIX 5.1. 


Reproducible: Always

Steps to Reproduce:
1. See details for info to reproduce
2.
3.

Actual Results:  
memory leak

Comment 1

[Mark Smith [:mcs]]

Strange that this only happens on AIX. I will have to try to reproduce this
based on the mozilla LDAP C SDK trunk code.

Can you pinpoint the leak more precisely? I can't remember the name of the tool,
but I know there is at least one Purify-like tool for AIX.

Do you make any calls to ldap_set_option()?

Comment 2

[edward.moraski]

Our latest version of the program makes a call to ldap_set_option however the 
previous did not and the leak still occurred.
You can test for the leak without a purify like tool by running a test program 
that tries (unsuccessfully) to bind repeatedly in a loop, then monitor the 
process memory usage with the shell command

ps -le | grep <program name> 

Comment 3

[Mark Smith [:mcs]]

Set target to 5.13. Currently working on a 5.12 release.

Comment 4

[Frankie]

Spam for bug 129472

Comment 5

[Mark Smith [:mcs]]

-> TM 5.14

Comment 6

[Jonathan]

Was this fixed? :)