Wasm build terminated with exit code 137

Open
#108,299 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
csharp, wasm
Domain
build-system

Research direction

Start by reviewing the linked out-of-memory issue and the Azure build results for build 1302057. Investigate why the Wasm build exits with code 137, then confirm the cause and define a reproducible validation for the resulting fix.

Written by the indexing model from the issue text.

Description

arch-wasm area-Infrastructure Known Build Error os-browser os-linux runtime-mono

This is similar to this out-of-memory issue from April: https://github.com/dotnet/runtime/issues/94077

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1302057

Error Message

{
  "ErrorMessage" : [ "Expected 0 exit code but got 137" ],
  "BuildRetry" : false,
  "ExcludeConsoleLog" : false
}
Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1302057
Error message validated: [Expected 0 exit code but got 137]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 2/20/2026 1:44:16 PM 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 metrics pending

Contributor guide

Open the contributing guide

First steps

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

More from dotnet/runtime

All issues in dotnet/runtime

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.