OutOfMemoryException in Test_Windows_Desktop_Release_32 Helix runs

[RikkiGibson]

Example CI runs:

• https://dev.azure.com/dnceng-public/public/_build/results?buildId=1264897&view=logs&j=eafb6fc7-5a7c-5786-9ccd-1a5efa236395&t=9d9d76b3-e635-5482-b6bc-de8204722db9&s=b4972d75-c06d-50c1-6307-90e4bda68063
• https://dev.azure.com/dnceng-public/public/_build/results?buildId=1264979&view=logs&s=d3c823a7-525b-53b3-522e-34d70e1d33c6

The active test run was aborted. Reason: Test host process crashed
Data collector 'Blame' message: procdump64.exe could not be found, please make sure that the executable is available on PATH. Alternatively set PROCDUMP_PATH environment variable to a directory that contains procdump64.exe executable.
Data collector 'Blame' message: The specified inactivity time of 15 minutes has elapsed. Collecting hang dumps from testhost and its child processes.
Data collector 'Blame' message: Dumping 7456 - testhost.net472.x86.
Results File: work-item-test-results.xml

Attachments:
  C:\h\w\A4CA0886\w\A31A08C7\e\235f0555-18a8-4c2a-bb6f-f7ba8e0bc5b3\Sequence_df8b2b98490e45fe86f56304661a2385.xml
  C:\h\w\A4CA0886\w\A31A08C7\e\235f0555-18a8-4c2a-bb6f-f7ba8e0bc5b3\testhost.net472.x86_7456_20260123T220923_hangdump.dmp
Test Run Aborted.
Total tests: Unknown
     Passed: 5022
    Skipped: 24
 Total time: 21.7693 Minutes

The active Test Run was aborted because the host process exited unexpectedly. Please inspect the call stack above, if available, to get more information about where the exception originated from.
The test running when the crash occurred: 
Microsoft.CodeAnalysis.Editor.CSharp.UnitTests.ConvertToRecord.ConvertToRecordCodeRefactoringTests.TestMovePropertiesAndProvideThisInitializerValuesWithNullOperations

This test may, or may not be the source of the crash.

I see different tests mentioned in different runs, but, tends to pretty consistently be in ConvertToRecordCodeRefactoringTests.

[chsienki]

Hit again on #83457:

Build	Failed leg	Workitem	Helix queue
1412942	Test_Windows_Desktop_Release_32 (attempt=2)	workitem_18	windows.amd64.vs2026.pre.scout.open
1413803	Test_Windows_Desktop_Release_32 (attempt=1)	workitem_18	windows.amd64.vs2026.pre.scout.open

Same workitem (workitem_18 -- runs Microsoft.CodeAnalysis.VisualBasic.EditorFeatures.UnitTests.dll) failed back-to-back in two separate builds. Cascade is identical to the original report:

System.TypeInitializationException : The type initializer for 'Roslyn.Test.Utilities.TargetFrameworkUtil' threw an exception.
---- System.OutOfMemoryException : Exception of type 'System.OutOfMemoryException' was thrown.
   at Roslyn.Test.Utilities.TargetFrameworkUtil.get_Mscorlib40References()
   at Roslyn.Test.Utilities.TargetFrameworkUtil.GetReferences(TargetFramework targetFramework)

The OOM in the static ctor takes out 1326-2110 dependent tests in one go, so a single occurrence forces a full leg rerun.

For broader context: across an audit of 65 recent dotnet/roslyn PRs, Test_Windows_Desktop_Release_32 was the #1 most-rerun job by ~2x (15 reruns vs the next-highest leg's 7).

[jjonescz]

Converted into a "known build error": #83640

That should not only automatically link future failing runs but also retry the CI run.