curl / Mailing Lists / curl-library / Single Mail
Buy commercial curl support from WolfSSL. We help you work out your issues, debug your libcurl applications, use the API, port to new platforms, add new features and more. With a team lead by the curl founder himself.

Re: Memory leak with curl_multi_socket_action

From: James Read via curl-library <curl-library_at_cool.haxx.se>
Date: Tue, 26 May 2020 16:30:17 +0100

On Tue, May 26, 2020 at 4:26 PM Daniel Stenberg <daniel_at_haxx.se> wrote:

> On Tue, 26 May 2020, James Read wrote:
>
> > So, I guess that's problem solved. Thanks.
>
> Lovely!
>
> With that issue nailed and perhaps with some newfound knowledge in your
> head,
> is there something we should think about to clarify or update in the
> documentation that would make this behavior clearer or less hard to the
> next
> user facing similar challenges?
>

I was working on code that a developer made for me. It was full of bugs.
Not just these memory leak issues. Upon close investigation it became clear
to me that he based the epoll/curl parts of his code largely on the example
at https://curl.haxx.se/libcurl/c/ephiperfifo.html

Perhaps this example could be updated to do a clean shutdown to avoid
confusion?

As far as the documentation goes. Seems pretty good to me.

James Read

>
> --
>
> / daniel.haxx.se | Commercial curl support up to 24x7 is available!
> | Private help, bug fixes, support, ports, new features
> | https://www.wolfssl.com/contact/
>

-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2020-05-26