At 11:57 AM +0100 11/3/04, Leopold Toetsch wrote:
Dan Sugalski <[EMAIL PROTECTED]> 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.
Cool, thanks.
--
Dan
--------------------------------------it's like this-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
