List:Internals« Previous MessageNext Message »
From:Patrick Lau Date:March 15 2009 10:59pm
Subject:Valgrind, MySQL - a single query mem check
View as plain text  
Hi all,

Unfortunately there is a memory leak in our code. Running the same
query several times increases the memory consumption of mysqld: in
Megabytes (9, 23, 90, 90, 90 ...)

I'm trying valgrind to detect the leak, but it gives me this....

LEAK SUMMARY:
==30826==    definitely lost: 2,828,751 bytes in 117,812 blocks.
==30826==    indirectly lost: 2,619,022 bytes in 75,051 blocks.
==30826==      possibly lost: 2,012 bytes in 72 blocks.
==30826==    still reachable: 3,058,698 bytes in 93,895 blocks.
==30826==         suppressed: 0 bytes in 0 blocks.

~2MB definitely lost... not the number I expected...

I think LEAK SUMMARY is about the whole process... Is there a way to
check mem consumption of a query thread using valgrind? How would you
handle such a case?

Thanks in advance!
Patrick
Thread
Valgrind, MySQL - a single query mem checkPatrick Lau16 Mar
  • Re: Valgrind, MySQL - a single query mem checkKristian Nielsen16 Mar
  • RE: Valgrind, MySQL - a single query mem checkIvan Novick16 Mar
    • Re: Valgrind, MySQL - a single query mem checkPatrick Lau16 Mar
      • Re: Valgrind, MySQL - a single query mem checkKristian Nielsen16 Mar
        • Re: Valgrind, MySQL - a single query mem checkPatrick Lau17 Mar
          • Re: Valgrind, MySQL - a single query mem checkJocelyn Fournier17 Mar
          • Re: Valgrind, MySQL - a single query mem checkKristian Nielsen17 Mar
  • Re: Valgrind, MySQL - a single query mem checkStewart Smith17 Mar
    • Re: Valgrind, MySQL - a single query mem checkPatrick Lau17 Mar