1. I'm using libcurl 7.11.1.
2. Statically linked.

Since we last spoke, I've discovered it only occurs when using libcurl with
SSL. I went back and used the standard version of libcurl - without ssl -
and all worked well - the handles were released properly. But, when I use
libcurl with ssl incorporated into it, the problem reappears.

If I open and close curl every time I want it to call it, a new handle is
created, but never released.
If I open curl only once and perform curl commands against that 1 instance
for the entire run of the program, it releases the handles properly.

I guess that's my solution - open curl only once. However, if I do that, but
then open a VPN connection and call curl, the connection will return with a
CURLE_OPERATION_TIMEDOUT message, then succeed on its 2nd attempt and add a
new handle which is never released. When I close the VPN tunnel, I receive a
CURLE_RECV_ERROR message the 1st time but succeed on the 2nd and again
create a handle which is never freed up.
Thanks in advance for any help you could provide. Jeff

-----Original Message-----
From: Daniel Stenberg [mailto:daniel-curl_at_haxx.se]
Sent: 041404 3:27 AM
To: libcurl development
Cc: emerson, jeff
Subject: Re: freeing up handles

On Tue, 13 Apr 2004, emerson, jeff wrote:

> Hi, I'm new to CURL and have come across a problem. When performing a
> curl_easy_perform under windows, I see that process handles are
incremented,
> but never released. Is this a bug, or am I doing something wrong?

1 - what libcurl version are you using?

2 - are you using it as a DLL or statically linked?

(I'm assuming "process handles" are what new thread/process are identified
with? - I'm a Windows cluebie.)

We've already got a minor memory leak reported (on Windows) and fixed when
libcurl was not used as a DLL. It would be interesting to hear if you see
these problems with a recent daily snapshot as well.

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