"Devendra Badhani" <[EMAIL PROTECTED]> writes: > Hi, > > I am using Netscape LDAP SDK ver 3.0 for > C, for doing some fast directory lookups. The > problem I am facing is that when I bombard > my application, which uses the ldap sdk, with > with a very high rate of directoruy lookup > requests, the memory usage of the process shoots > up. If I fire requests at a slower rate no memory > leaks are observed. Some memory leak tracing tools > indicate memory leaks in the sdk, especially for > the following calls : > --------------- > nslberi_calloc() > ber_alloc_t() > nsldapi_alloc_ber_with_options() > ---------------------- > > Are there known memory problems with this > version ( SDK ver 3.0 for C) ? If yes, will I have to > upgrade the SDK to a higher version? The product > I am working on is at a critical stage and upgrading > the SDK doen't sound like the best option > available ( will have to go through all the build > test cycles ... again). > > Any help on this will be highly appreciated.
I believe there are leaks in the 3.0 version, at least some of which have been fixed by newer SDK versions. One possible way you could avoid upgrading is to grovel through bonsai and cvsblame to figure out what the specific fixes are, and apply them to your local 3.0 tree. Upgrading to a newer version would be a fine thing, as newer versions have various other bugfixes (including threadsafety and deadlock fixes) as well. Dan
