Repository navigation
Wasm build terminated with exit code 137 #108299
Description
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
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 0 | 0 | 0 |
Activity
dotnet-policy-service commentedon Sep 26, 2024
Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.
dotnet-policy-service commentedon Sep 27, 2024
Tagging subscribers to this area: @BrzVlad, @kotlarmilos
See info in area-owners.md if you want to be subscribed.
[-][9.0] Wasm build terminated with exit code 137[/-][+]Wasm build terminated with exit code 137[/+]dotnet-policy-service commentedon Feb 23, 2026
Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.
jeffschwMSFT commentedon Apr 16, 2026
removing blocking-clean-ci as it has not failed in 30 days