Bugs item #1216500, was opened at 2005-06-07 18:13
Message generated for change (Comment added) made by bagder
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=1216500&group_id=976

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: libcurl
Group: bad behaviour
Status: Open
Resolution: None
Priority: 7
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Daniel Stenberg (bagder)
Summary: libcurl handle leak in Windows

Initial Comment:
In file 'hostthre.c' (Libcurl version 7.14.0) a new thread is
created:

/#ifdef _WIN32_WCE
  td->thread_hnd = (HANDLE) CreateThread(NULL, 0,
                                         
(LPTHREAD_START_ROUTINE) THREAD_FUNC,
                                         conn, 0, &td->thread_id);
  TRACE(("Created thread; %d\n", td->thread_id));
#else
  td->thread_hnd = (HANDLE) _beginthreadex(NULL, 0,
THREAD_FUNC,
                                           conn, 0, &td->thread_id);
#endif

The only place that CloseHandle is called on td-
>thread_hnd is in the function 'Curl_wait_for_resolv' in
the same file. HOWEVER, 'Curl_wait_for_resolv' does
not get called when I step through the code. Therefore
thread handles are being leaked.

Keep in mind that CreateThread/_beginthreadex DOES
get called.

My email address is kthyagar_at_hotmail.com

Thanks,
-Karthi.

----------------------------------------------------------------------

>Comment By: Daniel Stenberg (bagder)
Date: 2005-06-11 23:56

Message:
Logged In: YES
user_id=1110

Ok, I'll say this at once: if you don't respond within a few
days, we'll close this report considering it to be bogus.

----------------------------------------------------------------------

Comment By: Daniel Stenberg (bagder)
Date: 2005-06-09 00:52

Message:
Logged In: YES
user_id=1110

I've forwarded this bug report to the libcurl mailing list.
I don't personally have nor develop under Windows.

I assume you have verified emperically that libcurl leaks
this, or only by reading the source?

Can you please provide us with an as simple as possible
source code that uses libcurl and makes this leak occur?

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=1216500&group_id=976
_______________________________________________
http://cool.haxx.se/cgi-bin/mailman/listinfo/curl-tracker
Received on 2005-06-11