Debug-built WASM fails to load in wllama (works with release build)

[mitsunami]

Hi,
I’m trying to debug wllama by rebuilding the WASM with debug options, but I’m running into load/instantiation failures that don’t occur with the default release build.

Building the source as-is (release / optimized flags) works fine and the model loads correctly. However, when I rebuild with debug-related flags (e.g. -g2, ASSERTIONS, etc.), the WASM fails to load or instantiate in Chrome.

Depending on the build flags, I see errors such as:

* RangeError: Failed to set the 'length' property on 'Array': Invalid array length
* WebAssembly.instantiate(): Import #0 "env": module is not an object or function
* Failed to parse URL from wllama.wasm (when rebuilding with different Emscripten options)

This only happens with debug-built WASM — the same JS loader and runtime work fine with the release build.

I’m wondering:

• Has anyone else experienced issues loading debug-built WASM with wllama?
• Are there known incompatible Emscripten flags for wllama / llama.cpp in the browser?
• Are there recommended debug flag sets that are known to work?

Any guidance or known limitations around debug builds would be very helpful.
Thanks!