Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem: Please see upstream bug: https://jira.mariadb.org/browse/MDEV-10595
Version-Release number of selected component (if applicable): 5.5.50-1.el7_2
How reproducible: Always
Steps to Reproduce: See upstream bug.
Actual results: mysqld leaks memory
Expected results: mysqld does not leak memory
Additional info: Upstream fix is currently merged to their 5.5 branch, but not yet released. I have confirmed that applying the upstream fix to 5.5.50-1.el7_2 fixes the problem.
Thanks for the report, we should get this bug fixed as soon as RHEL 7 will include mariadb-5.5.52, which should be soon due to CVE fixes, since we rebase to latest upstream release for those security issues.