Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
5.5(EOL), 10.0(EOL), 10.1(EOL)
-
None
Description
https://bugs.mysql.com/bug.php?id=66740 describes a memory leak in older versions of libmysqlclient (from MySQL). I have an app suffering from this leak on CentOS 7 with the mariadb-libs 5.5.60 package it ships. I noticed that the -compat packages from downloads.mariadb.org offer a dropin libmysqlclient.so.18, but to my surprise, those also have the leak!
libmariadb.so.3 from MariaDB-shared does not leak (when compiled against, it's not a drop in replacement apparently).
Would it be possible to backport the fix for that leak from libmariadb to compat/libmysqlclient?
Attachments
Issue Links
Activity
Field | Original Value | New Value |
---|---|---|
Issue Type | Task [ 3 ] | Bug [ 1 ] |
Affects Version/s | 5.5 [ 15800 ] | |
Affects Version/s | 10.0 [ 16000 ] | |
Affects Version/s | 10.1 [ 16100 ] |
Priority | Minor [ 4 ] | Major [ 3 ] |
Fix Version/s | 5.5 [ 15800 ] | |
Fix Version/s | 10.1 [ 16100 ] |
Assignee | Oleksandr Byelkin [ sanja ] |
Remote Link | This issue links to "Bug #66740 Fix the mysql_thread_end cleanup bug in libmysql (Web Link)" [ 29001 ] |
Workflow | MariaDB v3 [ 92773 ] | MariaDB v4 [ 141171 ] |
There's another confirmed user affected, on RHEL7.
Example of memory leak :
==179== at 0x4C2B955: calloc (vg_replace_malloc.c:711)