Stream: beginners

Topic: wasm4 out of bounds

Kiryl Dziamura (Jan 24 2024 at 11:43):

I've been playing with wasm4 platform but ran into out of bounds error

here's an ugly prototype of a maze game. level 3 crashes. if to have a bigger field, let's say 20x20 (currently it's 6x6), the game crashes trying to build even the first level.

I thought it was something with recursion/stack overflow during random traversal. but it should be a pretty straightforward TCO case. also, there are no problems for the roc-cli platform, so it’s probably specific to the allocation mechanism of the wasm4 platform

https://gist.github.com/wontem/50bc86494a59fd7d7fffacc5dabb6e5d

bit_set.ArrayBitSet(u64,5120).isSet@http://localhost:4444/wasm4.js line 56 > WebAssembly.instantiate:wasm-function[6]:0x796
roc_alloc@http://localhost:4444/wasm4.js line 56 > WebAssembly.instantiate:wasm-function[4]:0x2b1
#UserApp_finishWalk_ab6bf482529beb271842e34a3922217532b2f57565d72aea510e9edbdcef6@http://localhost:4444/wasm4.js line 56 > WebAssembly.instantiate:wasm-function[95]:0xba67
#UserApp_continueWalk_49cb6ad1f356dc514791c661f63f6841479dc80eaa158e38e2871686552@http://localhost:4444/wasm4.js line 56 > WebAssembly.instantiate:wasm-function[90]:0xa86d
#UserApp_genMaze_9d55cb5018ba494bcf5765953355c83e4ade148e5c95b280aacd826c59bea86@http://localhost:4444/wasm4.js line 56 > WebAssembly.instantiate:wasm-function[87]:0xa36b
#UserApp_movePlayer_bad96aa871ccf5b068b2a1da7544fd3d07a932588efb92244e692b8beda99ce@http://localhost:4444/wasm4.js line 56 > WebAssembly.instantiate:wasm-function[84]:0x9d75
#UserApp_93_3efb3241b6f76bcf29426c5d5647f69b665c3ac3b1fc474c237e0eea46afd1@http://localhost:4444/wasm4.js line 56 > WebAssembly.instantiate:wasm-function[69]:0x802b
roc__mainForHost_2_caller@http://localhost:4444/wasm4.js line 56 > WebAssembly.instantiate:wasm-function[67]:0x7965
update@http://localhost:4444/wasm4.js line 56 > WebAssembly.instantiate:wasm-function[21]:0x1e59
bluescreenOnError@http://localhost:4444/wasm4.js:56:33222
update@http://localhost:4444/wasm4.js:56:35997
p@http://localhost:4444/wasm4.js:62:4760

Brendan Hansknecht (Jan 24 2024 at 16:16):

looks like it may be a bug with the allocator...not fully sure yet

Brendan Hansknecht (Jan 24 2024 at 16:30):

The error currently doesn't make sense to me. Looks to be failing an assert in zig but we have a conditional right before the assert that should make it impossible. Not yet sure what is going on. Will have to debug more later.

Kiryl Dziamura (Jan 25 2024 at 08:08):

Skimmed the allocator. Never read allocators or zig and must say, the code is very simple to follow! From what I see, it’s really hardly possible the problem happens because of the allocation for roc.

Looks more like it fails trying to allocate memory on the stack for zig, it just happens to fail during isSet. Will check it later today. Or maybe the trace log is not accurate

Kiryl Dziamura (Jan 25 2024 at 10:48):

Yeah, I decreased mem_size and increased stack_size by 10000 and it helped. Now, the question is why the stack overflow is happening. Seems to be a lack of TCO then. How can I check it? Going to check llvm ir, maybe there is a hint.

Brendan Hansknecht (Jan 25 2024 at 15:29):

Interesting. That makes sense for the random failure location.

Brendan Hansknecht (Jan 25 2024 at 15:33):

could be hitting this compiler bug: https://github.com/roc-lang/roc/issues/6213

Brendan Hansknecht (Jan 25 2024 at 15:34):

We need to cleanup our ir and ensure all stack allocas happen outside of looping code. Otherwise, as the loops run, it can still accumulate stack space.

Kiryl Dziamura (Jan 25 2024 at 16:56):

I used Task.loop as a workaround. Works well enough

Brendan Hansknecht (Jan 25 2024 at 17:03):

Glad you found a workaround

Last updated: Jul 06 2025 at 12:14 UTC