On Sun, May 24, 2020 at 4:07 PM Daniel Stenberg <dan...@haxx.se> wrote:
> On Sun, 24 May 2020, James Read via curl-library wrote: > > > Valgrind reports a memory leak in my web crawler: > > ... > > > What is memory being allocated for? > > Since your stack trace has no debug symbols it is hard for us to tell > exactyl > what's going on here. > OK > > > What do I need to free? > > If you use the libcurl API as documented, there should be nothing else to > free. > > > Is this a bug in curl or is something wrong at my end? > > I can't tell because there's not enough information. I would prefer a > stand-alone source code that can reproduce the problem or if that's too > hard, > maybe you could at least run a debug-version of libcurl with the symbols > present so that we can see a more descriptive stack trace there? > > How do I do that? I'm on ubuntu using packages. I guess this would mean installing from source with some special flags? > How often do you experience this leak? Do you know any triggers that make > it > more likely to happen? > The leak happens every time I run the application. There are many other similar messages from valgrind. I just included the one with the largest leak for brevity. James Read > > I don't think we have any known such memory leak (fixed since 7.68.0). > > -- > > / 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
