in reply to memory sieve discovery
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: memory sieve discovery
by Pstack (Scribe) on Jan 19, 2008 at 05:08 UTC | |
Here are some others: 651 /usr/lib/perl5/5.8.7/File/Path.pm line 121 582 /usr/lib/perl5/5.8.7/Math/BigInt.pm line 143 2947 /usr/lib/perl5/5.8.7/Math/BigInt.pm line 2303 1834 /usr/lib/perl5/5.8.7/Math/BigInt/Calc.pm line 1420 1472 /usr/lib/perl5/site_perl/5.8.7/HTML/TableExtract.pm line 1020 747 /usr/lib/perl5/site_perl/5.8.7/HTTP/Message.pm line 9 849 /usr/lib/perl5/site_perl/5.8.7/LWP.pm line 10 709 /usr/lib/perl5/site_perl/5.8.7/LWP/Protocol/http.pm line 416 1210 /usr/lib/perl5/site_perl/5.8.7/OLE/Storage_Lite.pm line 11 1194 /usr/lib/perl5/site_perl/5.8.7/OLE/Storage_Lite.pm line 712 2202 /usr/lib/perl5/site_perl/5.8.7/Regexp/Common.pm line 36 3924 /usr/lib/perl5/site_perl/5.8.7/Spreadsheet/ParseExcel.pm line 1929 1793 /usr/lib/perl5/site_perl/5.8.7/Spreadsheet/ParseExcel/Utility.pm line 11 1433 /usr/lib/perl5/site_perl/5.8.7/Spreadsheet/WriteExcel/Formula.pm line 25 2465 /usr/lib/perl5/site_perl/5.8.7/Spreadsheet/WriteExcel/Workbook.pm line 25 1311 /usr/lib/perl5/site_perl/5.8.7/URI/http.pm line 6 1012 /usr/lib/perl5/site_perl/5.8.7/i686-linux/BerkeleyDB.pm line 1441 551 /usr/lib/perl5/site_perl/5.8.7/i686-linux/Compress/Zlib.pm line 16 253 /usr/lib/perl5/site_perl/5.8.7/i686-linux/HTML/Entities.pm line 150 523 /usr/lib/perl5/site_perl/5.8.7/i686-linux/HTML/HeadParser.pm line 74 The leading number in this sample is just the leak count within 1 run of the application -- a batch process. And as I say, I dont know what, if any, significance to attach. Perhaps Exporter is excused, for instance, if globalising is considered "leaky" by definition. And so on. Pstack | [reply] |
by Corion (Patriarch) on Jan 19, 2008 at 13:22 UTC | |
I think at least part of this report is exaggerated. Devel::LeakTrace::Fast says that most of its reporting starts at INIT time to circumvent problems with symbol table aliasing. But the "early" reports for example for HTTP::Message (line 9) come because HTTP::Message uses require instead of use to load Carp.pm. My guess is that all modules by Gisle Aas , most notably all modules comprising LWP, will follow the same allocation pattern (that is, URI::http, LWP). Most likely, others will also follow this pattern. I think to separate the wheat from the chaff of the leaks reported by Devel::LeakTrace::Fast, you will have to write code that runs a small loop exercising exactly the code where the leak is reported, and then watch that program to see whether it grows beyond bounds or not. As another example, line 25 of SpreadSheet::WriteExcel::Formula seems to be the @ISA assignment - while that's using up memory, it's not generally considered a leak because that memory is still reachable. | [reply] [d/l] [select] |
by Pstack (Scribe) on Jan 19, 2008 at 21:05 UTC | |
cheers | [reply] |
by grinder (Bishop) on Jan 19, 2008 at 12:10 UTC | |
File::Path is pure-Perl, no XS components, so I'm hard pressed to explain what its leak might be. You could install the latest version and if the problem persists, file a bug report. I have a feeling, however, that your problem is more likely to be a coding style that happens to prevent temporaries from being freed at an appropriately early moment. • another intruder with the mooring in the heart of the Perl | [reply] |
by Pstack (Scribe) on Jan 19, 2008 at 20:39 UTC | |
| [reply] |
by syphilis (Archbishop) on Jan 19, 2008 at 10:56 UTC | |
Cheers, Rob | [reply] |
by Pstack (Scribe) on Jan 19, 2008 at 20:20 UTC | |
582 /usr/lib/perl5/5.8.7/Math/BigInt.pm line 143
| [reply] |