[users at i-scream] Probably leak of libstatgrab on Linux

[Jens Rehsack]

Lurking for leaks in Unix::Statgrab I run into this:

==32480== 63,488 bytes in 31 blocks are still reachable in loss record 103 of 103
==32480==    at 0x4C272B8: calloc (vg_replace_malloc.c:566)
==32480==    by 0x59CAEE1: build_trtable (regexec.c:3458)
==32480==    by 0x59CD17C: re_search_internal (regexec.c:2307)
==32480==    by 0x59CD292: regexec@@GLIBC_2.3.4 (regexec.c:253)
==32480==    by 0x6EBB44F: sg_get_network_io_stats_int (network_stats.c:612)
==32480==    by 0x6EBB6F1: sg_get_network_io_stats_r (network_stats.c:698)
==32480==    by 0x6CAB458: XS_Unix__Statgrab_get_network_io_stats (Statgrab.xs:180)
==32480==    by 0x4ABE26: Perl_pp_entersub (in /home/sno/perl5/perlbrew/perls/perl-5.20.0/bin/perl)
==32480==    by 0x7C795A5: leaktrace_runops (in /home/sno/perl5/perlbrew/perls/perl-5.20.0/lib/site_perl/5.20.0/x86_64-linux/auto/Test/LeakTrace/LeakTrace.so)
==32480==    by 0x43FE00: perl_run (in /home/sno/perl5/perlbrew/perls/perl-5.20.0/bin/perl)
==32480==    by 0x422264: main (in /home/sno/perl5/perlbrew/perls/perl-5.20.0/bin/perl)

Call it a reminder - it should be analyzed ...

Cheers
-- 
Jens Rehsack
rehsack at gmail.com