Been dabbling with wasm after the recent announcement, and my project crashes occasionally.
If you take the current version from GitHub and update Const TERRAIN_SIZE to 1024 in the main file, after a random number of level loads (skip using N), it dies, throwing a JS exception. Can take anywhere from single-figures to a couple of dozen, though happened after ~3 just now...
It doesn't seem to happen with my new size of 256, but I'd seen this before and only just got to trying to recreate.
Testing in latest Firefox on Windows 7 -- just tried it with Debug enabled and I get:
Cannot enlarge memory arrays. Either (1) compile with -s TOTAL_MEMORY=X with X higher than the current value 536870912, (2) compile with -s ALLOW_MEMORY_GROWTH=1 which allows increasing the size at runtime, or (3) if you want malloc to return NULL (0) instead of this abort, compile with -s ABORTING_MALLOC=0
Seems to be during/at end of level loading.
Original Author: DruggedBunny
Been dabbling with wasm after the recent announcement, and my project crashes occasionally.
If you take the current version from GitHub and update Const TERRAIN_SIZE to 1024 in the main file, after a random number of level loads (skip using N), it dies, throwing a JS exception. Can take anywhere from single-figures to a couple of dozen, though happened after ~3 just now...
It doesn't seem to happen with my new size of 256, but I'd seen this before and only just got to trying to recreate.
Testing in latest Firefox on Windows 7 -- just tried it with Debug enabled and I get:
Cannot enlarge memory arrays. Either (1) compile with -s TOTAL_MEMORY=X with X higher than the current value 536870912, (2) compile with -s ALLOW_MEMORY_GROWTH=1 which allows increasing the size at runtime, or (3) if you want malloc to return NULL (0) instead of this abort, compile with -s ABORTING_MALLOC=0Seems to be during/at end of level loading.