[browser][mono][MT] Uncaught TypeError: He._emscripten_force_exit is not a function

[pavelsavara]

Log

[10:48:35] info: MONO_WASM: Uncaught TypeError: He._emscripten_force_exit is not a function
                 Error
                     at Object.eo [as mono_exit] (http://127.0.0.1:37617/_framework/dotnet.js:4:24400)
                     at tt.config.exitOnUnhandledError.e.onerror (http://127.0.0.1:37617/_framework/dotnet.runtime.1f097nq1pv.js:3:207546)

[pavelsavara]

/azp run runtime-wasm

[dotnet-policy-service]

Tagging subscribers to 'arch-wasm': @lewing, @pavelsavara
See info in area-owners.md if you want to be subscribed.

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).

[azure-pipelines]

Azure Pipelines:
Successfully started running 3 pipeline(s).
13 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[Copilot]

Pull request overview

This PR updates the Mono browser build configuration (browser.proj) to export an additional Emscripten symbol when building with WasmEnableThreads=true, in response to a missing _emscripten_force_exit function at runtime.

Changes:

• Adds emscripten_force_exit to the list of exported Emscripten runtime methods under the threads-enabled condition.

[pavelsavara]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).

[pavelsavara]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

[pavelsavara]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).

[azure-pipelines]

Azure Pipelines:
Successfully started running 3 pipeline(s).
13 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.