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:
Memory consumption increases over time when using extensive the mariadb client.

The leak is caused by known bug which is fixed in upstream. 
https://bugs.mysql.com/bug.php?id=66740

However this bug is still observed in mariadb-libs-5.5.60-1.el7_5.x86_64 as shipped by RedHat.

Following is the example of memory leak :

==179== 2,080 bytes in 10 blocks are definitely lost in loss record 300 of 320
==179==    at 0x4C2B955: calloc (vg_replace_malloc.c:711)
==179==    by 0x9C50A36: ??? (in /usr/lib64/mysql/libmysqlclient.so.18.0.0)
==179==    by 0x9C15BC4: mysql_server_init (in /usr/lib64/mysql/libmysqlclient.so.18.0.0)
==179==    by 0x9C1CE96: mysql_init (in /usr/lib64/mysql/libmysqlclient.so.18.0.0)
==179==    by 0x99EAC9D: SMySQL::connect() (in /usr/lib64/pdns/libgmysqlbackend.so)

Version-Release number of selected component (if applicable):
mariadb-libs-5.5.60-1.el7_5.x86_64

How reproducible:
- Connect using mariadb multi-threaded client
- Memory leak is observed for each mysql connect

Steps to Reproduce:
1. Connect through client with several sessions
2. Observe the logs 

Actual results:
- Memory leaks are observed for each mysql connect

Expected results:
- No memory leak should happen. 


Additional info:

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: mariadb security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:4026