Bug 1689827

Summary:	[MariaDB Client] Memory leak of around 2 kb for every MySQL connect()
Product:	Red Hat Enterprise Linux 7	Reporter:	Ravindra Patil <ravpatil>
Component:	mariadb	Assignee:	Lukas Javorsky <ljavorsk>
Status:	CLOSED ERRATA	QA Contact:	Lukáš Zachar <lzachar>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	databases-maint, dhill, hhorak, ljavorsk, mmuzila, mschorm
Target Milestone:	rc	Keywords:	Reproducer
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-09-29 20:41:08 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1834835

Description Ravindra Patil 2019-03-18 08:59:16 UTC

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:

Comment 17 errata-xmlrpc 2020-09-29 20:41:08 UTC

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