Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[browser] avoid locks in ST interop #113046

Merged
merged 4 commits into from
Mar 6, 2025

Conversation

pavelsavara
Copy link
Member

Fixes #112734

@pavelsavara pavelsavara added arch-wasm WebAssembly architecture area-System.Runtime.InteropServices.JavaScript os-browser Browser variant of arch-wasm labels Mar 2, 2025
@pavelsavara pavelsavara added this to the 10.0.0 milestone Mar 2, 2025
@pavelsavara pavelsavara self-assigned this Mar 2, 2025
@pavelsavara pavelsavara marked this pull request as ready for review March 6, 2025 13:54
@pavelsavara pavelsavara requested a review from maraf March 6, 2025 13:54
@pavelsavara
Copy link
Member Author

/ba-g CI timeouts

@pavelsavara pavelsavara merged commit 7b627ed into dotnet:main Mar 6, 2025
145 of 148 checks passed
@pavelsavara pavelsavara deleted the browser_st_avoid_locks branch March 6, 2025 14:55
@srxqds
Copy link
Contributor

srxqds commented Mar 7, 2025

can you backport to release/9.0 ?

IDisposable added a commit to IDisposable/dotnet-runtime that referenced this pull request Mar 7, 2025
The '#ifdef` being tested is already known to be true because we're in the `#else` block of the previous test of `!FEATURE_WASM_MANAGED_THREADS` which is the same thing we were testing.
Noted in [this comment](dotnet#113046 (comment))
@pavelsavara
Copy link
Member Author

can you backport to release/9.0 ?

I'm not sure perf meets the risk/value requirements for the backport.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
arch-wasm WebAssembly architecture area-System.Runtime.InteropServices.JavaScript os-browser Browser variant of arch-wasm
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[mono] bug about wasm single thread using lock
6 participants