On Tuesday 24 of November 2009 19:53:04 Dantzler, DeWayne C wrote: > That is exactly what I did. I placed the calls for curl_global_init() and > curl_easy_init() in this order in a constructor and place the calls for > curl_global_cleanup() and curl_easy_cleanup() in the destructor. In fact, I > tried several different combinations in the destructor for the > curl_global_cleanup()and curl_easy_cleanup() methods, but each combination > had memory resource issues(see below). Now, I do call a 3rd party > library(Xerces) that also uses the curl library.
Please keep the conversation on list. You are doing something a bit different. It's not good idea to call curl_global_init()/curl_global_cleanup() more than once for nothing. I know there is something like a reference counter, but do not use it unless you really need to. Basically it's not thread-safe and it can trigger a memory leak under certain circumstances. If you want to get more help from us, you'll need to write something like a minimal example we can compile and run. Then it's easy for us to tell you what's actually wrong in your code. Kamil ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
