Sam Clegg

`emscripten_cancel_main_loop` should indeed make the thread joinable. Building with `-sRUNTIME_DEBUG` may help you see what the issue is? If the problem persists, perhaps you could build a small example showing...

Thanks for the repro case. This uncovered a bug in the browser main loop handling. I'm working on a fix now but you for a temporary fix you can set...

That certainly sounds like a separate issue.

> After creating a test case, it turns out that the memory allocation issue was caused by a thread using `Module.HEAP*` instead of just `HEAP*`, so it was not using...

Can you include the full backtrace? Is the `new` call coming from the main loop callback? Could you trry building with `-sPTHREADS_DEBUG`? Or perhaps you should share a failing example?...

I see, I assume we are treating `emscripten_pause_main_loop` the same as `emscripten_cancel_main_loop` in terms of keeping the runtime alive. One was to work around this an make sure your thread...

Is this a duplicate of https://github.com/emscripten-core/emscripten/issues/18112?

Context: https://github.com/WebAssembly/memory64/pull/50#discussion_r1647204142

I'm basically neutral on this. I've gotten used to calling it index type, so there is some inertia there I suppose.

@bvisness just FYI I've been doing all my recent spec work on the wasm-3.0 branch of this fork, not the main branch. This is so that all our work here...