On Thu, 9 Jun 2005, Gisle Vanem wrote:

>> HOWEVER, 'Curl_wait_for_resolv' does not get called when I step through the
>> code. Therefore thread handles are being leaked.
>
> AFAICS, Curl_wait_for_resolv() should always be called to clean-up the
> thread data. But maybe we should add code to Curl_destroy_thread_data() to
> close the thread handle too.

The fact that no one has reported this problem before makes me suspect this is
not actually a problem. If this reports is right, every single windows program
that uses a default built libcurl would leak handles.

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html