7.12.3

I'm pretty sure it's not a memory leak, because the amount of memory being used stays stable.

I'll try valgrind and lsof, thanks.

How would I use your built-in tools?

thanks,
Michael

-----Original Message-----
From: curl-library-bounces_at_cool.haxx.se on behalf of Daniel Stenberg
Sent: Mon 2/21/2005 11:48 AM
To: libcurl development
Subject: Re: Problem with file descriptors?
 
On Mon, 21 Feb 2005, Michael Mastroianni wrote:

> I think I'm probably running out of either sockets or file descriptors. I
> don't have a ton of linux experience (this problem doesn't happen to me on
> windows), and I was wondering if someone here could suggest approaches I
> should take to this problem.

You could use 'lsof' to check for used file handles. You should also check if
the size of the process libcurl is used in grows (in case of a memory leak).
We also have built-in memory leak tools and you can use valgrind or similar to
check for such.

What libcurl version are you using?

--
      Daniel Stenberg -- http://curl.haxx.se -- http://daniel.haxx.se
       Dedicated custom curl help for hire: http://haxx.se/curl.html