Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
perl.perl6.internals
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
parrot -t leaks like a sieve
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   3 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Dan Sugalski  
View profile  
 More options Nov 1 2004, 2:22 pm
Newsgroups: perl.perl6.internals
From: parrotbug-follo...@parrotcode.org (Dan Sugalski)
Date: Mon, 01 Nov 2004 11:22:41 -0800
Local: Mon, Nov 1 2004 2:22 pm
Subject: [perl #32270] parrot -t leaks like a sieve
Print | Individual message | Show original | Report this message | Find messages by this author
# 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


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Leopold Toetsch  
View profile  
 More options Nov 3 2004, 5:57 am
Newsgroups: perl.perl6.internals
From: l...@toetsch.at (Leopold Toetsch)
Date: Wed, 3 Nov 2004 11:57:52 +0100
Local: Wed, Nov 3 2004 5:57 am
Subject: Re: [perl #32270] parrot -t leaks like a sieve
Print | Individual message | Show original | Report this message | Find messages by this author

Dan Sugalski <parrotbug-follo...@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


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Dan Sugalski  
View profile  
 More options Nov 3 2004, 10:09 am
Newsgroups: perl.perl6.internals
From: d...@sidhe.org (Dan Sugalski)
Date: Wed, 3 Nov 2004 10:09:32 -0500
Local: Wed, Nov 3 2004 10:09 am
Subject: Re: [perl #32270] parrot -t leaks like a sieve
Print | Individual message | Show original | Report this message | Find messages by this author
At 11:57 AM +0100 11/3/04, Leopold Toetsch wrote:

>Dan Sugalski <parrotbug-follo...@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.

Cool, thanks.
--
                                Dan

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


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google