[perl #32270] parrot -t leaks like a sieve

[Dan Sugalski]

# New Ticket Created by Dan Sugalski
# Please include the string: [perl #32270]
# in the subject line of all future correspondence about this issue.
# <URL: http://rt.perl.org:80/rt3/Ticket/Display.html?id=32270 >

Throwing the trace switch on makes parrot leak. A *lot*. Processes
that top out at 100M VSIZE hit 1G or more, which, well... it ain't
good. Tracing's slow enough as it is without the added hit of
swapping and ever-increasing memory usage.
--
Dan

--------------------------------------it's like this-------------------
Dan Sugalski even samurai
d...@sidhe.org have teddy bears and even
teddy bears get drunk

[Leopold Toetsch]

Dan Sugalski <parrotbug...@parrotcode.org> wrote:

> Throwing the trace switch on makes parrot leak. A *lot*. Processes
> that top out at 100M VSIZE hit 1G or more, which, well... it ain't
> good. Tracing's slow enough as it is without the added hit of
> swapping and ever-increasing memory usage.

Yep. Tracing is using PIO_eprintf(), which finally is calling
Parrot_vsprintf_s(). Around that function call GC was disabled, so no
buffer memory got recycled, as the vast majority of buffer allocations
is coming from the trace.

Fixed.

leo

[Dan Sugalski]

Cool, thanks.