Could you try to run the command inside gdb then send me the backtrace ?
neko used over 2G process memory (on my 512M machine) under gdb,
and took 20 minutes to produce this stack trace.
Is it typical for neko compilations to use that much RAM, or is it a
symptom of a problem? Can neko be run in interpreted mode (without JIT)
or be forced to collect garbage more frequently?
This is a symptom of the problem. Looks like the neko_module_jit method
start an infinite loop that allocates memory when compiled with -O3 on
your OS. Could you try to investigate the sources in neko/vm/jit_x86.c
and check what is going wrong ?
Best,
Nicolas
--
Neko : One VM to run them all
(http://nekovm.org)
