Bugs item #1216500, was opened at 2005-06-07 09:13
Message generated for change (Tracker Item Submitted) made by Item Submitter
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: wrong behaviour
Status: Open
Resolution: None
Priority: 5
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.

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

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-07