Ticket #1804 (closed bug: fixed)

Opened 4 years ago

Last modified 4 years ago

Parrot out of mem on building Rakudo

Reported by: tadzik Owned by:
Priority: normal Milestone:
Component: build Version: trunk
Severity: medium Keywords:
Cc: Language:
Patch status: Platform:

Description

My Rakudo compilation died due to "Parrot VM: PANIC: Out of mem!". Full compilation log attached. Rakudo was using Parrot r49277.

Attachments

log Download (16.1 KB) - added by tadzik 4 years ago.
compilation log

Change History

Changed 4 years ago by tadzik

  • attachment log Download added

compilation log

follow-up: ↓ 2   Changed 4 years ago by jkeenan

  • component changed from none to build

This *may* be due to a problem we've been noticing lately: much increased memory requirements for compilation for both Parrot and Rakudo Perl.

With regard to Parrot:  this current thread on list

With regard to Rakudo Perl:  RT #76828

Do the problems described there seem similar to what you experienced?

Can you post output from uname -a and from top as I did in the second link above?

Thank you very much.

kid51

in reply to: ↑ 1   Changed 4 years ago by jkeenan

Do the problems described there seem similar to what you experienced?

Answering my own question ...

/home/tjs/rakudo/rakudo/parrot_install/bin/parrot  \
  src/gen/perl6.pbc --target=pir  \
	            src/gen/core.pm > src/gen/core.pir
	Failed allocation of 4096 bytes
	Parrot VM: PANIC: Out of mem!
	C file src/gc/alloc_memory.c, line 61

... these lines from your attachment due look very close to RT #76828.

kid51

  Changed 4 years ago by tadzik

from top: Mem: 1225552k total, 1190420k used, 35132k free, 444736k buffers

uname -a: Linux feather 2.6.32-5-xen-amd64 #1 SMP Tue Jun 1 06:38:33 UTC 2010 x86_64 GNU/Linux

About the similar problem, I haven't experienced any hungup, it just crashed, like the log shows.

Thank you very much. Ted

  Changed 4 years ago by coke

  • status changed from new to closed
  • resolution set to fixed

tadzik reports this is now closable.

Note: See TracTickets for help on using tickets.