[debian-mysql] Bug#1001467: mariadb-10.5: Backport MariaDB 10.5.13 fixes? (Particularly MDEV-26712)

Xan Charbonnet xan at charbonnet.com
Fri Dec 10 16:37:23 GMT 2021


Source: mariadb-10.5
Version: 10.5.12-0+deb11u1
Severity: important

Dear Maintainer,

I've been investigating an issue where my MariaDB server ends up running away
with the RAM on the machine.  I believe it may be caused by MDEV-26712 [1],
which is a memory leak bug.

According to the MariaDB 10.5.13 release notes [2], this was fixed in that
release.  I see a number of other fixes as well.

Are there any plans to backport these fixes to Bullseye, or to move Bullseye
to 10.5.13?

I should mention that I'm not 100% sure that this is the fix to my problem:
apparently this problem applies to earlier versions as well, and I don't have
this issue on earlier versions.  So it may be something else.  Regardless
of my particular situation, the MariaDB in Bullseye does contain this bug
that can consume any amount of RAM.

[1] https://jira.mariadb.org/browse/MDEV-26712
[2] https://mariadb.com/kb/en/mariadb-10513-release-notes/




-- System Information:
Debian Release: 11.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-9-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled



More information about the pkg-mysql-maint mailing list