runtime-diagnostics cDAC_windows_x64_release pipeline is broken

[akoeplinger]

It's broken all the time: https://dev.azure.com/dnceng-public/public/_build?definitionId=309&_a=summary

I see this assertion in the Standard_Console_Output.log:

        STDIN: 00:00.708: !runcommand !ClrStack
        00:00.718: OS Thread Id: 0x140c (0)
        00:00.728:         Child SP               IP Call Site
        STDERROR: 00:00.739: Process terminated. Assertion failed.
        STDERROR: 00:00.739: cDAC: 80004001, DAC: 0
        STDERROR: 00:00.739:    at System.Diagnostics.DebugProvider.Fail(String, String) + 0x49
        STDERROR: 00:00.739:    at System.Diagnostics.Debug.Fail(String, String) + 0x58
        STDERROR: 00:00.739:    at System.Diagnostics.Debug.Assert(Boolean, String, String) + 0x2d
        STDERROR: 00:00.739:    at System.Diagnostics.Debug.Assert(Boolean, String) + 0x28
        STDERROR: 00:00.739:    at System.Diagnostics.Debug.Assert(Boolean, Debug.AssertInterpolatedStringHandler&) + 0x3a
        STDERROR: 00:00.739:    at Microsoft.Diagnostics.DataContractReader.Legacy.ClrDataMethodInstance.Microsoft.Diagnostics.DataContractReader.Legacy.IXCLRDataMethodInstance.GetILOffsetsByAddress(ClrDataAddress, UInt32, UInt32*, UInt32*) + 0x784
        STDERROR: 00:00.739:    at <Microsoft_Diagnostics_DataContractReader_Legacy_IXCLRDataMethodInstance>F4F0D8D2301DBFC096F02E180BF918816583194AFC454FEA155744418AC237781__InterfaceImplementation.ABI_GetILOffsetsByAddress(ComWrappers.ComInterfaceDispatch*, UInt64, UInt32, UInt32*, UInt32*) + 0xdd
    }
    Process 4764 exited 57005 (00:01.482 elapsed)

[dotnet-policy-service]

Tagging subscribers to this area: @steveisok, @dotnet/dotnet-diag
See info in area-owners.md if you want to be subscribed.

[MihuBot]

I'm a bot. Here is a possible related and/or duplicate issue (I may be wrong):

• [DAC][windows] Tests failed: SOS.UnitTests_net8.0_x64.html #120317

[mdh1418]

It looks like the builds from main started breaking after these commits 11702c4...efe20ba

[mdh1418]

It looks like #121418 might be fixing this already? The cDAC_windows_x64_release pipeline only has one alternate failure for that PR