New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
perl 5.8.4 memory leak with "slurp" I/O style #7835
Comments
From nico-kw-perlbug.be9b7b@gianniotis.orgThe following code fragment, from the FAQ, exhibits a memory leak for open(FIND, "find /terrabyte1/ro -type f -print |") or die;; My data set is approx 161,000 files totaling slightly over 1 Tb. When If I refactor the do {} block to not "slurp" the file in but compute Platform details: % perl -V Characteristics of this binary (from libperl): |
From @smpeters
Valgrind seems to confirm the leaks. ==9320== warning: Valgrind's siglongjmp is incomplete |
The RT System itself - Status changed from 'new' to 'open' |
From @smpeters
Wow! I had been periodically checking this, but something has changed ==22372== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 24 from 1) |
@smpeters - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#34417 (status was 'resolved')
Searchable as RT34417$
The text was updated successfully, but these errors were encountered: