WASM memory model makes it very similar to an environment with very restricted virtual address space, where we don't want to reserve large blocks of memory upfront (since they also get 'committed' right away). It is also an environment where this restriction can be very tight (< 32 MB).
Right now, the default 32 bit config reserves something like ~50MB of memory on startup, which is pretty large, and this number doesn't respect the WASM memory limits because the necessary code is 64-bit only.
Is fixing that "just work" or something trickier?
Ref: #85844.
Context: dotnet/runtimelab#3150.
WASM memory model makes it very similar to an environment with very restricted virtual address space, where we don't want to reserve large blocks of memory upfront (since they also get 'committed' right away). It is also an environment where this restriction can be very tight (< 32 MB).
Right now, the default 32 bit config reserves something like ~50MB of memory on startup, which is pretty large, and this number doesn't respect the WASM memory limits because the necessary code is 64-bit only.
Is fixing that "just work" or something trickier?
Ref: #85844.
Context: dotnet/runtimelab#3150.