Sam Clegg

How are you calling a function from --post-js from your native code? In general, native code shouldn't be able to call those symbols. (Are you building with `-sERROR_ON_DEFINED_SYMBOLS=0` perhaps?)

Oh .. I see, you not actually calling the functions from C, you calling them from inline JS inside of C. In that case two things. (1) You can probably...

I think this is a duplicate of #21866 (which I just transferred from the emsdk repo)

If possible, I think think would be a lot more actionable if you could narrow this down. In doing so you could also reveal more about the divergence.

Unaligned accesses are allowed in Wasm, so you can use `-sSAFE_HEAP=2` to ignore the alignment fault.

> This issue is not limited to localhost. Can you describe how/when you are able to reproduce the issue? Any idea what set of circumstances cause it?

A full set of link flags at least would be very useful in diagnosing.

> @sbc100 @juj @kripken Any update here I am encountering this as well when using localhost. Don't believe i have seen this in any production but its a pain point...

> @sbc100 Nothing obvious, we have been using emscripten for a few years, and part of our CI process runs GTests through emrun that run quite a bit of code...

> Sure > > ``` > -sINITIAL_MEMORY=100MB > -sSTACK_SIZE=2MB > -fexceptions > -sWASM_BIGINT > -sALLOW_MEMORY_GROWTH > -sMALLOC=mimalloc > -sEXIT_RUNTIME > --post-js forward-env.js > -pthread > -sPROXY_TO_PTHREAD > -Os > --emrun...