memory leaks in mozilla LDAP C SDK

RESOLVED INCOMPLETE

Status

Directory
LDAP C SDK
RESOLVED INCOMPLETE
9 years ago
6 years ago

People

(Reporter: Meena Vyas, Unassigned)

Tracking

({mlk})

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.8.1.2) Gecko/20070225 Firefox/2.0.0.2
Build Identifier: leaks

I can see some memory leaks in mozilla LDAP C SDK :
===================================
umem_alloc_1344 leak: 4 buffers, 1344 bytes each, 5376 bytes total
umem_alloc_1344 leak: 6 buffers, 1344 bytes each, 8064 bytes total
libumem.so.1`malloc+0x27
libumem.so.1`calloc+0x47
libldap60.so`nslberi_calloc+0x3c
libldap60.so`ber_alloc_t+0x37
libldap60.so`nsldapi_alloc_ber_with_options+0xf4
libldap60.so`simple_bind_nolock+0x3ed
libldap60.so`ldap_simple_bind+0xbd
===================================
umem_alloc_40 leak: 10 buffers, 40 bytes each, 400 bytes total
umem_alloc_24 leak: 8 buffers, 24 bytes each, 192 bytes total
libumem.so.1`malloc+0x27
libsocket.so.1`get_addr+0x1b8
libsocket.so.1`_getaddrinfo+0x483
libsocket.so.1`getaddrinfo+0x19
libnspr4.so`PR_GetAddrInfoByName+0xab
libprldap60.so`prldap_connect+0xf5
libldap60.so`nsldapi_connect_to_host+0x115
libldap60.so`nsldapi_new_connection+0x369
libldap60.so`nsldapi_open_ldap_defconn+0xcc
libldap60.so`nsldapi_send_server_request+0x4fc
libldap60.so`nsldapi_send_initial_request+0xb6
libldap60.so`simple_bind_nolock+0x4d9
===================================
umem_alloc_24 leak: 8 buffers, 24 bytes each, 192 bytes total
umem_alloc_32 leak: 6 buffers, 32 bytes each, 192 bytes total
umem_alloc_32 leak: 4 buffers, 32 bytes each, 128 bytes total
umem_alloc_64 leak: 2 buffers, 64 bytes each, 128 bytes total
umem_alloc_64 leak: 6 buffers, 64 bytes each, 384 bytes total
umem_alloc_40 leak: 10 buffers, 40 bytes each, 400 bytes total
umem_alloc_40 leak: 6 buffers, 40 bytes each, 240 bytes total
umem_alloc_40 leak: 4 buffers, 40 bytes each, 160 bytes total
umem_alloc_40 leak: 8 buffers, 40 bytes each, 320 bytes total
umem_alloc_24 leak: 10 buffers, 24 bytes each, 240 bytes total

libumem.so.1`malloc+0x27 / libumem.so.1`calloc+0x47
libldap60.so`ldap_x_calloc+0x3c / (libldap60.so`ldap_x_malloc+0x3a AND libldap60.so`nsldapi_strdup+0x40 )
[ libldap60.so`ldap_x_hostlist_next+0x146 ]
libldap60.so`ldap_x_hostlist_first+0x146
 OR
[ libnspr4.so`PR_Calloc+0x5e  AND libprldap60.so`prldap_socket_arg_alloc+0x2a ]

libprldap60.so`prldap_connect+0xb2
libldap60.so`nsldapi_connect_to_host+0x115
[ libldap60.so`nsldapi_new_connection+0x3b ]
libldap60.so`nsldapi_open_ldap_defconn+0xcc
libldap60.so`nsldapi_send_server_request+0x4fc
libldap60.so`nsldapi_send_initial_request+0xb6
libldap60.so`simple_bind_nolock+0x4d9
libldap60.so`ldap_simple_bind+0xbd 

Reproducible: Always

Steps to Reproduce:
1. I checked out using cvs -d :pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot co -P -rLDAPCSDK_6_0_5_RTM DirectorySDKSourceC  
2. Ran ome tests
3.
(Reporter)

Updated

9 years ago
OS: Solaris → OpenSolaris
For reference, what tests did you run?
(Reporter)

Comment 2

9 years ago
I am unable to reproduce it today. That day there was a network problem one of the ldap server was down.

Updated

8 years ago
Keywords: mlk
I mark this as INCOMPLETE because it isn't easily reproducible and it refers to a really old version of Firefox.
Feel free to reopen!
Status: UNCONFIRMED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.