hooray! the result of ldap_get_dn() wasn't being freed.
patches committed into cvs, but i havent built a new release yet..
is anyone else running their eye over the code?
d
--
David Leonard Dav...@cs...
Dept of Comp. Sci. and Elec. Engg _ Room:78-640 Ph:+61 7 336 51187
The University of Queensland |+| http://www.csee.uq.edu.au/~leonard/
QLD 4072 AUSTRALIA ~` '~ B73CD65FBEF4C089B79A8EBADF1A932F13EA0FC8
---------- Forwarded message ----------
Date: Fri, 18 Aug 2000 10:47:42 +1000
From: Dr. Ross Lazarus <ro...@me...>
To: David Leonard <dav...@cs...>
Subject: Re: search_s leaks in tiny amounts
bingo. 15000 cycles and the memory footprint hasn't shifted.
Is it worth exercising a few more functions this way? It's a really dumb
python test script!
Could be automated by doing a system call to free and parsing the
results.
Oh yes, forgot. Thesis due soon.... {O-:)
Thanks !
David Leonard wrote:
>
> On Fri, 18 Aug 2000, Dr. Ross Lazarus typed thusly:
>
> > Thanks for the suggestion - hmmmnn - patch failed on all hunks but I cut
> > and pasted from a windoze mail reader to a unix box...
> > So I did it by hand -
> > Minor syntax problemo -
>
> yeah should have moved it into the bottom of the block instead :)
> i did that after i emailed you. its the leak for sure...
>
> entrytuple = Py_BuildValue("(sO)", dn, attrdict);
> Py_DECREF(attrdict);
> PyList_Append(result, entrytuple);
> Py_DECREF(entrytuple);
> free(dn);
> }
> ldap_msgfree( m );
> return result;
|
