glibc 2.26 memory leak with MySQL?

DJ Delorie dj@redhat.com
Mon Aug 14 14:54:00 GMT 2017


> Do we have a rebased tracer against glibc 2.26?

I don't but I can, might take a bit to rebase that branch.

Meanwhile, a quick test is to disable the per-thread cache through
glibc's tunables, to at least see if that's part of the problem.

export GLIBC_TUNABLES=glibc.malloc.tcache_count=0



More information about the Libc-help mailing list