[Known Build Error] Test_Windows_Desktop_Release_32: Test host process crashed

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=1520534&view=logs&j=4f4b926f-8abe-5536-d4a9-2361289b3c74 Build error leg or test failing: Windows_Release_Desktop / Test_Windows_Desktop_Release_32 / Run Unit Tests Pull request: https://github.com/dotnet/roslyn/pull/84575

Error Message

{
  "ErrorMessage": "The active test run was aborted. Reason: Test host process crashed",
  "ErrorPattern": "",
  "BuildRetry": true,
  "ExcludeConsoleLog": false
}

Additional details

Recurring testhost.net472.x86 crash on the Test_Windows_Desktop_Release_32 leg (windows.amd64.vs2026.pre.scout.open Helix queue), not correlated with PR content — same signature (different failing test assembly each time) observed across multiple unrelated main builds in the same window:

• Build 1520534 (PR #84575) — crash after Microsoft.VisualStudio.LanguageServices.LiveShare.UnitTests.ProjectsHandlerTests
• Build 1520424 (main) — crash after Microsoft.CodeAnalysis.LanguageServer.Protocol.UnitTests started
• Build 1520169 (main) — same Release_32 job failure

No crash dump is captured (Data collector 'Blame' message: procdump.exe could not be found, please make sure that the executable is available on PATH), so the underlying exception type can't be confirmed from the console log alone, but the pattern matches prior closed issues about 32-bit OOM crashes on this same leg: #82135, #83640.

Likely related root causes to investigate:

• x86 (32-bit) testhost memory pressure on windows.amd64.vs2026.pre.scout.open — consider further partitioning Release_32.
• procdump.exe missing from PATH on this queue image, preventing crash dump collection for diagnosis.

Known issue validation

Build: :mag_right: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1520534 Error message validated: [The active test run was aborted. Reason: Test host process crashed] Result validation: :white_check_mark: Known issue matched with the provided build. Validation performed at: 7/22/2026 1:09:48 AM UTC

Report

Summary