Andy Dougherty (via RT) wrote:
With a a fresh checkout (r9274) I get a number of errors where parrot eventually
gobbles up all the memory on the system. Here's the first such one:
t/op/gc........................
# Failed test (t/op/gc.t at line 279)
# './parrot --gc-debug "/home/doughera/src/parrot/parrot-andy/t/op/gc_13.pir"'
failed with exit code 131
# Looks like you failed 1 test of 22.
Strange. The test succeeds on linux/86 and OS/X 10.3 darwin. Running it
through valgrind on the linux box doesn't show any indication of an error.
t/op/gc_13 is using continuations for backtracking and a few closures.
Maybe you can compare used features of other failing tests, so that the
error reason can be narrowed a bit.
A debug session could also reveal some error cause.
leo
