I can use some help here. If I have a smaller file, like the 10000 lines I use for my perl6 timings, with this script:
--8<---
use 5.18.2;
use warnings;
use Text::CSV_XS;
my $csv = Text::CSV_XS->new ({ auto_diag => 1 });
open my $fh, "<", "/tmp/hello.csv";
my $r = $csv->getline_all ($fh, 9000, 0);
-->8---
hello.csv is taken from the CSV game
https://bitbucket.org/ewanhiggs/csv-game only fewer lines
sh$ for i in $(seq 1 10000); do echo 'hello,","," ",world,"!"'; done > /tmp/hello.csv
sh$ time perl csv.pl < /tmp/hello.csv
$ export PERL_DESTRUCT_LEVEL=2 PERL_DL_NONLAZY=1
$ valgrind \
--suppressions=sandbox/perl.supp \
--leak-check=yes \
--leak-resolution=high \
--show-reachable=yes \
--num-callers=50 \
--log-fd=3 \
/pro/bin/perl \
-MPerl::Destruct::Level=level,2 \
sandbox/rt116085.pl \
Show quoted text 3>valgrind.log
That ends with
==9925== LEAK SUMMARY:
==9925== definitely lost: 0 bytes in 0 blocks
==9925== indirectly lost: 0 bytes in 0 blocks
==9925== possibly lost: 0 bytes in 0 blocks
==9925== still reachable: 4,592 bytes in 13 blocks
==9925== suppressed: 0 bytes in 0 blocks
==9925==
==9925== For counts of detected and suppressed errors, rerun with: -v
==9925== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Valgrinds manual (
http://valgrind.org/docs/manual/faq.html#faq.deflost) tells me not to worry:
"still reachable" means your program is probably ok -- it didn't free some memory it could have. This is quite common and often reasonable. Don't use --show-reachable=yes if you don't want to see these reports.
A simple
$ valgrind perl sandbox/rt116085.pl
==17010== Memcheck, a memory error detector
==17010== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==17010== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==17010== Command: perl sandbox/rt116085.pl
==17010==
==17010==
==17010== HEAP SUMMARY:
==17010== in use at exit: 2,421,076 bytes in 8,501 blocks
==17010== total heap usage: 28,427 allocs, 19,926 frees, 4,887,993 bytes allocated
==17010==
==17010== LEAK SUMMARY:
==17010== definitely lost: 26,820 bytes in 19 blocks
==17010== indirectly lost: 63,954 bytes in 27 blocks
==17010== possibly lost: 2,327,235 bytes in 8,446 blocks
==17010== still reachable: 3,067 bytes in 9 blocks
==17010== of which reachable via heuristic:
==17010== newarray : 11,288 bytes in 350 blocks
==17010== suppressed: 0 bytes in 0 blocks
==17010== Rerun with --leak-check=full to see details of leaked memory
==17010==
==17010== For counts of detected and suppressed errors, rerun with: -v
==17010== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Which might indicate what you are experiencing, but I cannot lay a finger on the root cause
$ make leakcheck
PERL_DESTRUCT_LEVEL=2 PERL_DL_NONLAZY=1 valgrind --suppressions=sandbox/perl.supp --leak-check=yes --leak-resolution=high --show-reachable=yes --num-callers=50 --log-fd=3 "/pro/bin/perl" "-MPerl::Destruct::Level=level,2" "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t 3>valgrind.log
t/00_pod.t ........ ok
t/01_pod.t ........ ok
t/10_base.t ....... ok
t/12_acc.t ........ ok
t/15_flags.t ...... ok
t/20_file.t ....... ok
t/21_lexicalio.t .. ok
t/22_scalario.t ... ok
t/30_types.t ...... ok
t/40_misc.t ....... ok
t/41_null.t ....... ok
t/45_eol.t ........ ok
t/46_eol_si.t ..... ok
t/50_utf8.t ....... ok
t/51_utf8.t ....... ok
t/55_combi.t ...... ok
t/60_samples.t .... ok
t/65_allow.t ...... ok
t/70_rt.t ......... ok
t/75_hashref.t .... ok
t/76_magic.t ...... ok
t/77_getall.t ..... ok
t/78_fragment.t ... ok
t/79_callbacks.t .. ok
t/80_diag.t ....... ok
t/81_subclass.t ... ok
t/85_util.t ....... ok
t/90_csv.t ........ ok
t/91_csv_cb.t ..... ok
All tests successful.
Files=29, Tests=50529, 82 wallclock secs (71.33 usr 0.38 sys + 42.43 cusr 0.55 csys = 114.69 CPU)
Result: PASS
==17030== by 0x506DE5: Perl_pp_require (in /pro/bin/perl)
==17030== by 0x4BE535: Perl_runops_standard (in /pro/bin/perl)
==17030== by 0x446A68: perl_run (in /pro/bin/perl)
==17030== by 0x420A58: main (in /pro/bin/perl)
==17030==
==17030== LEAK SUMMARY:
==17030== definitely lost: 603 bytes in 9 blocks
==17030== indirectly lost: 0 bytes in 0 blocks
==17030== possibly lost: 0 bytes in 0 blocks
==17030== still reachable: 12,168 bytes in 34 blocks
==17030== suppressed: 0 bytes in 0 blocks
==17030==
==17030== For counts of detected and suppressed errors, rerun with: -v
==17030== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)
Shows me that all leaks are in perl itself (or I misinterpret that data, which is quite possible).
This is perl 5, version 24, subversion 0 (v5.24.0) built for x86_64-linux-thread-multi-ld
