Hi guys:

I've been running gmetad 3.1.0.1273 on my test server since April 21st
and noticed that the RSS for gmetad has grown to ~653m.

It looks like we have another memory leak, folks.

Here's what I could gather from valgrind:

==18713== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 32 from 2)
==18713== malloc/free: in use at exit: 234,032 bytes in 2,508 blocks.
==18713== malloc/free: 25,484 allocs, 22,976 frees, 4,686,738 bytes allocated.
==18713== For counts of detected errors, rerun with: -v
==18713== searching for pointers to 2,508 not-freed blocks.
==18713== checked 84,432,220 bytes.
==18713==
==18713== 377 (52 direct, 325 indirect) bytes in 1 blocks are
definitely lost in loss record 12 of 25
==18713==    at 0x40056BF: calloc (vg_replace_malloc.c:279)
==18713==    by 0x4021BE2: dotconf_create (dotconf.c:718)
==18713==    by 0x804EE37: parse_config_file (in /usr/sbin/gmetad)
==18713==    by 0x804A28E: main (in /usr/sbin/gmetad)
==18713==
==18713==
==18713== 1,088 bytes in 8 blocks are possibly lost in loss record 16 of 25
==18713==    at 0x40056BF: calloc (vg_replace_malloc.c:279)
==18713==    by 0x818B0A: _dl_allocate_tls (in /lib/ld-2.3.4.so)
==18713==    by 0xA639DE: pthread_create@@GLIBC_2.1 (in
/lib/tls/libpthread-2.3.4.so)
==18713==    by 0x804A458: main (in /usr/sbin/gmetad)
==18713==
==18713==
==18713== 8,612 (240 direct, 8,372 indirect) bytes in 30 blocks are
definitely lost in loss record 20 of 25
==18713==    at 0x4004405: malloc (vg_replace_malloc.c:149)
==18713==    by 0x4023EB8: datum_dup (hash.c:34)
==18713==    by 0x402456D: hash_lookup (hash.c:321)
==18713==    by 0x8049F8F: sum_metrics (in /usr/sbin/gmetad)
==18713==    by 0x40246BA: hash_foreach (hash.c:417)
==18713==    by 0x804A073: do_root_summary (in /usr/sbin/gmetad)
==18713==    by 0x40246BA: hash_foreach (hash.c:417)
==18713==    by 0x804A585: main (in /usr/sbin/gmetad)
==18713==
==18713== LEAK SUMMARY:
==18713==    definitely lost: 292 bytes in 31 blocks.
==18713==    indirectly lost: 8,697 bytes in 33 blocks.
==18713==      possibly lost: 1,088 bytes in 8 blocks.
==18713==    still reachable: 223,955 bytes in 2,436 blocks.
==18713==         suppressed: 0 bytes in 0 blocks.
==18713== Reachable blocks (those to which a pointer was found) are not shown.
==18713== To see them, rerun with: --show-reachable=yes

Hope this helps.

Cheers,

Bernard

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft 
Defy all challenges. Microsoft(R) Visual Studio 2008. 
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Ganglia-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ganglia-developers

Reply via email to