emscriptten built wasm module didn't load and had crash in reactjs project.

[Realitian]

Hi,
I tried to build wasm as single-thread mode by set USE_PTHREADS=0 and tried to load it in a simple threejs based react-js project.
But it failed to load and crashed with following error.

Uncaught (in promise) RuntimeError: memory access out of bounds
at emHdBindings.wasm:0x5c7ae4
at emHdBindings.wasm:0x5ca39e
at emHdBindings.wasm:0x52afbf
at emHdBindings.wasm:0x537a96
at emHdBindings.wasm:0x6591c4
at emHdBindings.wasm:0x52bbdc
at emHdBindings.wasm:0x3e44d8
at emHdBindings.wasm:0x3e413b
at emHdBindings.wasm:0x1839c
at emHdBindings.wasm:0x18001

Btw, it worked with webpack based threejs-vanillar project.
It is strange why it does not work in reactjs based.
Please advice me if anybody has clue.

@kaischroeder , Could you check my issue?

[hybridherbst]

Ran into the same issue (needle-tools/usd-viewer#7) and it might be a Windows-only problem with local development – the same works fine on Mac and Linux machines.

Before that error, on Windows there's a log regarding files not being found (file /usd/plugInfo.json couldn't be read):

[michaelybecker]

+1, on multiple projects that leverage the runtime - all fail on PCs when run locally, all work on mac.

[pecasha]

I think I found the reason. It is a problem with the emHdBindings.data file.
Just use this linked file to replace in your project.
https://www.usdz-viewer.net/wasm/emHdBindings.data

---

The line separator of the emHdBindings.data file seems to need to be LF, but in the Windows, it will be automatically converted to CRLF during git commit, which leads to this error.

You can add .gitattributes configuration to solve the problem of line separators.

*.data text eol=lf