Paul Fox wrote:
> > Actually no - I specifically don't want to go though a tar/untar step > > because for some reason on my FreeBSD 5.4 box BackupPC_tarCreate has a > > memory leak that causes it to fail after a few thousand files. I was > > looking for a way round that bug. > >you're probably already way on top of this, but a bug in >BackupPC_tarCreate that was suspected to be a memory leak turned >out (sometime within the last month) to be a perl typo in the >routine that writes the tar archive. > >so, are you sure it's a memory leak? > >okay, i just went and checked my mail archives, and see from your >original symptoms that it does indeed look a whole lot like a >memory leak, but it's probably worth trying the fix anyway, if >you haven't already done so. (it's easy: at line 230 in >BackupPC_tarCreate, change "my $fh = @_;" to "my ($fh) = @_;".) > >paul > > > I don't think that's it (although I did apply the patch) - there are no hardlinks in the data set in question so that shouldn't trigger the leak - what I'm seeing is an increase in the size of the perl process that's running theBackupPC_tarCreate that seem to be proportional to the number of files processed (that is it grows slower with big files than it does with small ones). Does anybody have any magic perl tricks to catch memory leaks that they'd like to share? John ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ BackupPC-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
