Bugs item #3130914, was opened at 2010-12-07 02:46
Message generated for change (Comment added) made by bagder
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=3130914&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: client module
Group: bad behaviour
>Status: Closed
>Resolution: Invalid
Priority: 5
Private: No
Submitted By: sam sharma (sam-sharma)
Assigned to: Daniel Stenberg (bagder)
Summary: curl_easy_cleanup doesn't call curl_global_cleanup

Initial Comment:
The curl_easy_init api calls the curl_global_init but respective curl_easy_cleanup doesn't call the curl_global_cleanup at all; hence memory leaks.

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

>Comment By: Daniel Stenberg (bagder)
Date: 2010-12-07 08:32

Message:
This is intentional.

First, the documentation clearly says you should use curl_global_init()
and only when the app fails to adhere to the recommendation libcurl tries
to survive by forcing a call to it by itself.

Most importantly however, is that curl_easy_cleanup() cannot call
curl_global_cleanup() reliably and thread-safe so it does not.

This is not a bug.

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

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=3130914&group_id=976
Received on 2010-12-07