[browser][coreCLR] linear memory, mmap, GC #121036

Activity

1. pavelsavara

   added this to the 11.0.0 milestone on Oct 23, 2025
2. pavelsavara

   self-assigned this

   on Oct 23, 2025
3. pavelsavara

   added

   arch-wasmWebAssembly architectureWebAssembly architecture

   area-GC-coreclr

   os-browserBrowser variant of arch-wasmBrowser variant of arch-wasm

   on Oct 23, 2025
4. github-project-automation

   added this to AppModelon Oct 23, 2025
5. dotnet-policy-service commented on Oct 23, 2025

   

   dotnet-policy-serviceBot

   on Oct 23, 2025 – with Dotnet Policy Service

   Contributor

   More actions

   Tagging subscribers to 'arch-wasm': @lewing, @pavelsavara
   See info in area-owners.md if you want to be subscribed.
6. dotnet-policy-service commented on Oct 23, 2025

   

   dotnet-policy-serviceBot

   on Oct 23, 2025 – with Dotnet Policy Service

   Contributor

   More actions

   Tagging subscribers to this area: @dotnet/gc
   See info in area-owners.md if you want to be subscribed.
7. MihuBot commented on Oct 23, 2025

   

   MihuBot

   on Oct 23, 2025

   More actions

   I'm a bot. Here is a possible related and/or duplicate issue (I may be wrong):

   • [wasm] High memory fragmentation on LOS allocations #118044
8. pavelsavara commented on Oct 23, 2025

   

   pavelsavara

   on Oct 23, 2025

   MemberAuthor

   More actions

   Mono related fixes for the same problem

   • [wasm] Fix fragmentation caused by large objects allocation #118099
   • [wasm] stop using mmap/munmap #108512
9. pavelsavara

   closed this as completedin #127328on May 7, 2026
10. github-actions

    locked and limited conversation to collaborators on Jun 6, 2026