[browser][MT] JSHostImplementation.CallEntrypoint - The handle is invalid

Open

#109,636 opened on Nov 8, 2024 1 comment 0 reactions 1 assignee View on GitHub

@pavelsavara is already working on this.

Since Nov 8, 2024.

Assessment

This issue has not been assessed yet.

Description

arch-wasm area-VM-threading-mono disabled-test os-browser

Log

[18:14:00] info: 006 |           -    : isRunning:false isAttached:false isEventLoop:false reuseCount:  0 - emscripten-pool
JavaScript error: http://127.0.0.1:39061/_framework/dotnet.runtime.js, line 3: Error: The handle is invalid.
[18:14:00] fail: [0x000ebc38--UI- 18:14:00.975] MONO_WASM: The handle is invalid.
                    at System.Reflection.MethodBase.GetMethodFromHandle(RuntimeMethodHandle handle)
                    at System.Runtime.InteropServices.JavaScript.JSHostImplementation.CallEntrypoint(IntPtr assemblyNamePtr, String[] args, Boolean waitForDebugger)
                 ManagedError@http://127.0.0.1:39061/_framework/dotnet.runtime.js:3:37412
                 un@http://127.0.0.1:39061/_framework/dotnet.runtime.js:3:27191
                 cn/<@http://127.0.0.1:39061/_framework/dotnet.runtime.js:3:26754
                 ql</</<@http://127.0.0.1:39061/_framework/dotnet.runtime.js:3:201014
                 ql</<@http://127.0.0.1:39061/_framework/dotnet.runtime.js:3:201135
                 callUserCallback@http://127.0.0.1:39061/_framework/dotnet.native.js:8:98666
                 createDotnetRuntime/safeSetTimeout/createDotnetRuntime<@http://127.0.0.1:39061/_framework/dotnet.native.js:8:106269
[18:14:01] info: WASM EXIT 1

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=863764&view=logs&jobId=f02b8cf9-dd4d-54fc-c292-2bb1d305b019
Build error leg or test failing:

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "MONO_WASM: The handle is invalid",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=863764
Error message validated: [MONO_WASM: The handle is invalid]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 11/8/2024 11:55:26 AM UTC

Report

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	0	0

Dominant language: C#
Stars: 18.3k
Forks: 5.6k
PR merge metrics: PR metrics pending

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

Tsavorite.test fails to compile on main: TestBase.cs references Garnet.test.TestUtils, which is not linked into Tsavorite.test.csproj Open

Difficulty 2/5 1-3 hours Newbie friendliness 86/100

microsoft/garnet#2161 · 2 comments · Opened Sep 20, 2026
v11 update: Validation attributes are no longer experimental Open

:watch: Not Triaged 11.0 fundamentals/subsvc

Difficulty 2/5 1-3 hours Newbie friendliness 92/100

dotnet/AspNetCore.Docs#37699 · Opened Sep 20, 2026
SE 5.3.0 beta 7: In Settings Video player download buttons aren't together Open

Difficulty 2/5 1-3 hours Newbie friendliness 72/100

SubtitleEdit/subtitleedit#15108 · 1 comment · Opened Sep 20, 2026
Kubernetes get-started create-component.md: Go and C# silently default isMinikube instead of requiring it, unlike TS/Python/Java/HCL Open

area/docs-content Bug pulumi/docs

Difficulty 1/5 1-3 hours Newbie friendliness 94/100

pulumi/docs#21762 · Opened Sep 20, 2026
Create parent directories only after the containment check in InstallHelper.TryExtractToDirectory Open

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

PowerShell/PSResourceGet#2056 · Opened Sep 20, 2026

More C# issues