life icon indicating copy to clipboard operation
life copied to clipboard

Strange misbehaviour in life VM

Open singpolyma-shopify opened this issue 5 years ago • 4 comments

https://0x0.st/zcgm.wasm

The above wasm works in nodejs and using wagon's wasm-run command, but running with life I get a different return value.

Calling the exported function run with no arguments should return 4 and in nodejs and wasm-run it does but running under life I get 0.

I know it's a big blob but I have not yet been able to get a smaller version that triggers the bug.

singpolyma-shopify avatar May 02 '19 17:05 singpolyma-shopify

Thanks for reporting the bug!

Could you try with Polymerase engine enabled? There's a known bug in the register allocator for interpreter mode.

losfair avatar May 03 '19 01:05 losfair

That's the AOT mode? When I enable that it takes a looong time and then says "unable to open compiled code"

singpolyma-shopify avatar May 03 '19 13:05 singpolyma-shopify

Has this bug solved? Can life be used in production env?

lowesyang avatar Jul 19 '19 02:07 lowesyang

I haven't tested this specific case in awhile, but in general we have had much more luck with AOT (though you can't run it under many Docker setups because of the userfaultfd requirement)

singpolyma-shopify avatar Jul 19 '19 13:07 singpolyma-shopify