# Possible memory leak in 5.0.67 b7

**URL:** <https://forums.percona.com/t/possible-memory-leak-in-5-0-67-b7/1011>\
**Category:** Other MySQL® Questions\
**Created:** [November 26, 2008, 5:02pm UTC](https://forums.percona.com/t/possible-memory-leak-in-5-0-67-b7/1011 "2008-11-26T17:02:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![avinson](https://avatars.discourse-cdn.com/v4/letter/a/f9ae1b/32.png) [@avinson](https://forums.percona.com/u/avinson)\
**Post date:** [November 26, 2008, 5:02pm UTC](https://forums.percona.com/t/possible-memory-leak-in-5-0-67-b7/1011/1 "2008-11-26T17:02:24Z")

</div>

I run a MySQL cluster with a single master and multiple slaves. All systems are running MySQL enterprise 5.0.56. I decided to experiment with the latest percona release on one of the slaves to see if there was a significant difference in performance. What I’m seeing is that the mysqld process slowly grows in memory size until eventually the system starts swapping. I thought it was possible that the percona release used slightly more memory overall so I reduced innodb buffer pool from 24G to 20G but I am still seeing the same behavior. It looks like there may be a memory leak or there is a setting that I need that I don’t have. Here are my relevant config options:

skip-locking  
key\_buffer\_size = 256M  
max\_allowed\_packet = 16M  
table\_cache = 256  
sort\_buffer\_size = 8M  
myisam\_sort\_buffer\_size = 8M

innodb\_buffer\_pool\_size = 20G  
innodb\_log\_file\_size = 256M  
innodb\_file\_per\_table = 1  
innodb\_thread\_concurrency = 0  
innodb\_file\_io\_threads = 10  
innodb\_max\_dirty\_pages\_pct = 70  
innodb\_flush\_method = O\_DIRECT  
innodb\_support\_xa = 0

query\_cache\_type = 1  
query\_cache\_size = 64M  
long\_query\_time = 1  
max\_connections = 2048  
thread\_cache\_size = 32

With 24G innodb buffer pool size on the 5.0.56 enterprise binary the mysqld process is stable at 27G resident size in memory. The 5.0.67 percona binary steadily grows until it overwhelms the system. Is there a setting I’m missing? Any help is appreciated.

-Aaron

---

<div class="post-metadata">

**Author:** ![flauret](https://avatars.discourse-cdn.com/v4/letter/f/65b543/32.png) [@flauret](https://forums.percona.com/u/flauret)\
**Post date:** [January 21, 2009, 7:14pm UTC](https://forums.percona.com/t/possible-memory-leak-in-5-0-67-b7/1011/2 "2009-01-21T19:14:49Z")

</div>

hello,

sorry to up an old post but i think i am suffering of the same trouble and wanted to know if it is something well declared or not

my settings are debian lenny withe mysql 5.0.67 b7 with yasufumi patch and i am suffering of the same situation of growing in memory up to the swap and memory saturation/crash.

mysql 5.0.32 unmodified does not give me this trouble(just some other because i run with bi xeon quad…)  
so this is the reporting if someone can tell us more about this situation. it might be great to know if i/we missed something in our settings.

regards  
frederic