This is the mail archive of the libc-help@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: glibc 2.26 memory leak with MySQL?


On 12 August 2017 at 19:49, Michael Brunnbauer <brunni@netestate.de> wrote:
> since upgrading from glibc-2.23 to 2.26, I have observed out of memory errors
> in 2 different mysql deployments after 2-3 days of runtime:
>
> 170812 15:51:42 [ERROR] /usr/bin/mysqld: Out of memory (Needed 1675264 bytes)
> 170812 15:52:01 [ERROR] /usr/bin/mysqld: Out of memory (Needed 1677712 bytes)
>
> I've never had such Problems with those mysql deployments before and one
> of them is configured for very modest memory usage.
>
> I use mysql 5.5.57 and Kernel 3.16.46. glibc has been compiled with gcc-4.9.4
> like this:
>
>  echo "CFLAGS += -march=i686" > configparms
>  ../configure --enable-add-ons --prefix=/usr --enable-kernel=2.6.25 --host=i686-pc-linux-gnu
>
> MySQL has not been recompiled since upgrading glibc and gcc (previous version
> 4.8.5).
>
> Have there been any changes that can explain this, e.g. the per-thread cache
> for malloc?

The malloc cache may be the reason, especially since building with
--disable-experimental-malloc seems to solve this.  If you're willing
to help isolate the problem, can you check if any of the
glibc.malloc.tcache* tunables help resolve the problem?

https://www.gnu.org/software/libc/manual/html_node/Memory-Allocation-Tunables.html#Memory-Allocation-Tunables

Siddhesh


-- 
http://siddhesh.in


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]