On Fri, Aug 22, 2008 at 06:46:42PM -0600, Max L. Eidswick wrote:
> ---------- ok here is the updated info as of Aug 22 2008
>
> The memory leak is in libcurl (very sure)
> It takes a lot of iterations to discover it
> It happens in secondary Win32 threads (don't forget to close the thread handle)
> It is also in 7.18.2, no change that I can see
> It is not a consistent number of bytes per iteration
>
> That's about all.

Since it's a threaded app, have you followed all the rules about
multithreaded use of libcurl? Including the rule about not calling
curl_global_init from within a thread? Have you ruled out a memory leak
happening from within an application callback?

>>> Dan

-- 
http://www.MoveAnnouncer.com              The web change of address service
          Let webmasters know that your web site has moved