On Thu, Jul 20, 2017 at 12:37 PM, Timo Paulssen wrote:
> On 19/07/17 21:52, Gabor Szabo wrote:
>> Hi,
>>
>> is it possible to get the size of memory used by the current Perl 6
>> process? (From inside the code)
>> Is it possible to get the size of the individual variables?
>>
>> Gabor
>
> I'm not
On 19/07/17 21:52, Gabor Szabo wrote:
> Hi,
>
> is it possible to get the size of memory used by the current Perl 6
> process? (From inside the code)
> Is it possible to get the size of the individual variables?
>
> Gabor
I'm not aware of something cross-platform that rakudo offers for memory
use
Hi,
is it possible to get the size of memory used by the current Perl 6
process? (From inside the code)
Is it possible to get the size of the individual variables?
Gabor
Peter Gibbs wrote:
Clinton A. Pierce wrote:
LOOP: new P1, .PerlHash
branch LOOP
This is simply a long-standing GC bug. Try the attached patch and see if
it helps.
Thanks for clarifying this. Actually, when introducing GC_IS_MALLOC I
was bug compatible too ;-)
Patch included in Parrot_
Clinton A. Pierce wrote:
> LOOP: new P1, .PerlHash
> branch LOOP
> What happens is that memory gets chewed up
> quickly. Do I have the wrong idea of how the Px registers are used to
point
> to things (god, I hope not) or is there some GC that needs to happen that
> isn't (and I can expect it t
I'm in the middle of a rather large project, and stopped to do a memory
usage sanity check. To my surprise I found a leak and traced it back to
the way I was allocating PerlHashes and whatnot.
To boil it down further, look at this PASM:
LOOP: new P1, .PerlHash
branch LOOP
Wha
