This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: glibc 2.26 memory leak with MySQL?
- From: DJ Delorie <dj at redhat dot com>
- To: "Carlos O'Donell" <carlos at redhat dot com>
- Cc: brunni at netestate dot de, libc-help at sourceware dot org
- Date: Mon, 14 Aug 2017 10:54:07 -0400
- Subject: Re: glibc 2.26 memory leak with MySQL?
- Authentication-results: sourceware.org; auth=none
- Authentication-results: ext-mx06.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx06.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=dj at redhat dot com
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com CC843267C8
> 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