-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Wasm build terminated with exit code 137 #108299
Copy link
Copy link
Open
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tabarch-wasmWebAssembly architectureWebAssembly architecturearea-Infrastructureos-browserBrowser variant of arch-wasmBrowser variant of arch-wasmos-linuxLinux OS (any supported distro)Linux OS (any supported distro)runtime-monospecific to the Mono runtimespecific to the Mono runtime
Milestone
Description
Metadata
Metadata
Assignees
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tabarch-wasmWebAssembly architectureWebAssembly architecturearea-Infrastructureos-browserBrowser variant of arch-wasmBrowser variant of arch-wasmos-linuxLinux OS (any supported distro)Linux OS (any supported distro)runtime-monospecific to the Mono runtimespecific to the Mono runtime
Type
Projects
StatusShow more project fields
No status
This is similar to this out-of-memory issue from April: #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