Stories
Slash Boxes
Comments

NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

use Perl

All the Perl that's Practical to Extract and Report

sub r {return if !$_[0]; r($_[0]-1); } leaktrace{ r(1);}; More | Login | Reply

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Re: sub r {return if !$_[0]; r($_[0]-1); } leaktra (Score:1)

by daxim (8218)

#p5p
[16:49] <shadowpaste> "daxim" at 217.168.150.38 pasted "recursion does not release memory for reuse?" (14 lines) at http://paste.scsys.co.uk/45082 [16:49] <dipsy> [ magnet_web paste from "daxim" at 217.168.150.38... ] [16:49] <daxim> what's going on here? [16:50] <Zefram> fragmentation? [16:50] <purl> fragmentation is interesting [16:50] <Nicholas> no, Pad frames created for recursion are not released [16:50] <Nicholas> the assumption is that you'll recurse again [16:
- Re: sub r {return if !$_[0]; r($_[0]-1); } leaktra (Score:1)
  
  by jozef (8299) on 2010.06.22 12:48 (#72101) Homepage Journal
  
  perl -MTest::LeakTrace -le 'sub r {return if !$_[0]; r($_[0]-1); } r(1); leaktrace{ r(1);};'
  Hmm yes the second recursion calling is not leaking memory any more.
  
  Reply to This
  
  Parent

Get More Comments

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.