percona-discussion team mailing list archive

[nicholas <nicholas@xxxxxxxxx>]

Yasufumi Kinoshita wrote:
> nicholas,
> 
> Sorry, I couldn't specify which source file may have problem by current
> information.
> 
> Please tell me the full information from "show global variables;" and
> "show innodb status\G" at the memory leak.
> 
> Thank you,
> Yasufumi
> 

Hello,
this was a hot production system, so we have replaced the troublesome
-67 version with a less patched -68 version. So unfortunately we do not
have show innodb status\G or show global variables\G from the leaking
system. Vadim got a copy of my.cnf and global variables, from when the
system already was "downgraded" to -68.

Since then our memory usage  has been dead stable. Since it is a hot
production sytem we do not want to experiment too much. Our test systems
with the same builds did not show the same results, so we might have to
tag this unreproducible and just keep an eye open for possible memory leaks.

-nicholas

-- 
Possible memory leak in the MySQL Binaries Percona build10
https://bugs.launchpad.net/bugs/315619
You received this bug notification because you are a member of Percona
developers, which is the registrant for Percona patches.

Status in Patches for MySQL by Percona: New

Bug description:
Hello, we have been using the 67-b10 version since around release, and we see a memory usage development that would indicate a memory leak?

Server version: 5.0.67-percona-highperf-b10-log MySQL Percona High Performance Edition (GPL)

http://nicholas.users.linpro.no/mysql-memory-month.png

Week 50 we ran stock redhat mysql . Early week 51 we installed the percona version. since then memory usage has been growing. Last week orso it ran out of swap space, so we added some more today ;)

We also run http://www.percona.com/mysql/5.0.68/RPM/rhel5/ another place, without the same problems.

greetings
-nicholas