diff options
| author | Simon Tatham <anakin@pobox.com> | 2021-04-16 18:07:15 +0100 |
|---|---|---|
| committer | Simon Tatham <anakin@pobox.com> | 2021-04-16 18:07:15 +0100 |
| commit | 8fa545c76c35dd7954220eb172a1783044794168 (patch) | |
| tree | bfe7f0fd45bcd825f0ab7d6bf563d7af5f46ae42 /nestedvm.c | |
| parent | f8b15bab6b2a8dd8309cdef3dc49ae3377cb997d (diff) | |
| download | puzzles-8fa545c76c35dd7954220eb172a1783044794168.zip puzzles-8fa545c76c35dd7954220eb172a1783044794168.tar.gz puzzles-8fa545c76c35dd7954220eb172a1783044794168.tar.bz2 puzzles-8fa545c76c35dd7954220eb172a1783044794168.tar.xz | |
Set ALLOW_MEMORY_GROWTH in the Emscripten build.
How embarrassing. When I updated the Emscripten build to use WASM, a
major reason I bothered to do it at all was that I'd heard that WASM
was capable of reallocating its memory arena larger on the fly. Turns
out that it _can_, but only if you specifically set the option in
Emscripten to allow it.
With this option set, I can finish a 25x25 Galaxies, where previously
the game would crash part way through (and not even a very large part)
with errors about memory growth in the Javascript console.
Diffstat (limited to 'nestedvm.c')
0 files changed, 0 insertions, 0 deletions