Thank you again for your input! This is running on an embedded device with a total of 2 GiB of RAM, so nothing close to 32GB would be possible on this context.

And for more context, the tables we're working with are TINY by cloud standards. They are all 2-3 columns and less than 200 rows in total. With that this is sounding more and more like a corrupted/uninitialized value is making its way into a call to stack_grow().

I tried running your above example (edited to remove what I assumed was an extra 0) and got the following:

Modification of non-creatable array value attempted, subscript -16777217 at ./test.pl line 7.