Skip to content

[wasm][coreclr] Use 4GB limit for corerun#124633

Merged
radekdoulik merged 1 commit intodotnet:mainfrom
radekdoulik:clr-wasm-4GB-corerun
Feb 22, 2026
Merged

[wasm][coreclr] Use 4GB limit for corerun#124633
radekdoulik merged 1 commit intodotnet:mainfrom
radekdoulik:clr-wasm-4GB-corerun

Conversation

@radekdoulik
Copy link
Member

And enable disabled test.

This is follow up to #123377 where this change was disabled as potential problem when looking for regression.

And enable disabled test
@radekdoulik radekdoulik added this to the Future milestone Feb 20, 2026
Copilot AI review requested due to automatic review settings February 20, 2026 09:35
@dotnet-policy-service
Copy link
Contributor

Tagging subscribers to this area: @agocke, @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the WASM/CoreCLR corerun host to allow growth up to a 4GB WebAssembly linear memory limit, and re-enables a previously skipped JIT regression test that exercises very large array allocations.

Changes:

  • Increase corerun’s Emscripten -sMAXIMUM_MEMORY from 2GB to 4GB for browser/wasm builds.
  • Remove the WASM-targeted ActiveIssueAttribute skip from jit64/regress/vsw/373472 to re-enable the test on WASM.

Reviewed changes

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

File Description
src/tests/JIT/jit64/regress/vsw/373472/test.il Removes the WASM ActiveIssueAttribute so the large-array regression runs on WASM again.
src/coreclr/hosts/corerun/CMakeLists.txt Raises Emscripten maximum memory setting to 4GB so large allocations required by runtime tests can succeed.

@radekdoulik
Copy link
Member Author

/ba-g the failures are unrelated

@radekdoulik radekdoulik merged commit f4d21a8 into dotnet:main Feb 22, 2026
127 of 132 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants