Re: Help tracking down libcurl + nss memory leak
Date: Wed, 8 Apr 2009 20:16:29 +0200 (CEST)
On Wed, 8 Apr 2009, Toshio Kuratomi wrote:
> has been doing work here as well::
> From reading that thread, I think the current thought is that this is a leak
> caused by incorrectly using the libcurl API. I have a simple test case that
> I want to run by you to see what the right use of the API is::
If that code leaks memory with recent versions of libcurl and NSS, I would
claime it is very likely to be an actual and proper bug!
> Is using the inner curl_global_cleanup the correct behavior?
> Is there something besides curl_easy_cleanup() I should be calling to
> release memory from the CURL easy handle?
> I'm guessing this is a bug in the libcurl+nss or nss library but I'd like to
> know my test case is fine before launching into that code.
Did you try to build debug versions of the libs and run valgrind on the test
app to see where the memory is allocated? I'll try to give it shot myself...
-- / daniel.haxx.seReceived on 2009-04-08