Bug#327611: perl: Memory leak in repetition operator.

Dominic Hargreaves dom at earth.li
Sun Sep 8 15:35:53 UTC 2013


On Sun, Sep 11, 2005 at 10:40:13PM +0100, Andrew Suffield wrote:
> On Sun, Sep 11, 2005 at 07:52:22PM +0400, Andrew Shirrayev wrote:

> > Memory allocated, not release and not use for lesser object.
> 
> Oh, hmm, that's probably perl's own arena allocator logic getting
> confused and failing to reuse the space. Deep voodoo, I'm not touching
> that.
> 
> > Object (temporary buffer?) stay in memory w/o any reference.
> 
> Stack copies. Same thing. As far as I can tell, perl thinks they're
> freed, it's just failing to put the next object in a sensible place.
> 
> To quote from the documentation:
> 
>        Perl is a profligate wastrel when it comes to memory use.
>        There is a saying that to estimate memory usage of Perl, assume
>        a reasonable algorithm for memory allocation, multiply that
>        estimate by 10, and while you still may miss the mark, at least
>        you won't be quite so astonished.  This is not absolutely true,
>        but may provide a good grasp of what happens.

Given all this, I don't see the value of keeping this report open in
the BTS. So far it seems that there is no evidence of an actual leak
(in which case the subject line would at least be inaccurate) and the
other issues are mostly an inherent part of perl's design.

Any objections to me closing this?

Dominic.




More information about the Perl-maintainers mailing list