I have a strong suspicion that this bug is related to https://github.com/parrot/parrot/issues/795 . As demonstrated in that issue, Parrot tends to gobble up all available memory even in a simple case of allocating and releasing an array, and once the process is at the edge of its memory allocation limits various panics can easily ensure.
It might very well be something else, but I just wanted to point out the known issue with Parrot's GC in this context. Pm
