.NET 10: csc fails with Failed to create CoreCLR, HRESULT: 0x80070008

[rolfbjarne]

Description

csc fails to run with:

Failed to create CoreCLR, HRESULT: 0x80070008

Reproduction Steps

Repro script:

#!/bin/bash -ex

curl -LO https://ci.dot.net/public/Sdk/10.0.100-rtm.25520.117/dotnet-sdk-10.0.100-osx-arm64.tar.gz
mkdir dotnet
cd dotnet
tar xvf ../dotnet-sdk-10.0.100-osx-arm64.tar.gz
cd ..
DOTNET_ROOT=$(pwd)/dotnet ./dotnet/sdk/10.0.100/Roslyn/bincore/csc --help

This is a simplified version of what we're running into, here's a binlog of that: msbuild.binlog.zip

Expected behavior

csc succeeds

Actual behavior

+ ./dotnet/sdk/10.0.100/Roslyn/bincore/csc --help
Failed to create CoreCLR, HRESULT: 0x80070008

Regression?

Yes, this started happening in this maestro bump: dotnet/macios#24064 (first commit)

Known Workarounds

No response

Configuration

No response

Other information

No response

[MihuBot]

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

• Failed to create CoreCLR, HRESULT: 0x8007000C #96247

[jjonescz]

0x80070008 seems to mean "ERROR_NOT_ENOUGH_MEMORY"
There doesn't seem to be anything interesting changed between 20.105 and 20.117 versions of the SDK (dotnet/dotnet@5aef8ea...50d7970), so I guess this might be a problem in your pipeline, like insufficient disk space on the CI machines

[rolfbjarne]

I guess this might be a problem in your pipeline, like insufficient disk space on the CI machines

I can reproduce locally, and I have plenty of disk space available.

[jjonescz]

Thanks. Looks like some issue with the apphost then. @agocke how do we investigate further what is the failure here?

Since this seems to be macOS specific, it might be something with signing, but as I said above, there don't seem to be any interesting changes between the relevant .NET builds.

Note: confirmed with @rolfbjarne offline that renaming the csc apphost makes the build work again since it falls back to using dotnet exec csc.dll instead of the csc apphost, hence my conclusion that this is some problem with the apphost.

[dotnet-policy-service]

Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov
See info in area-owners.md if you want to be subscribed.

[vitek-karas]

Can you enable COREHOST tracing and repro it? The trace will give lot more detail on what's happening in the apphost.
https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-environment-variables#corehost_trace

[rolfbjarne]

Can you enable COREHOST tracing and repro it? The trace will give lot more detail on what's happening in the apphost. learn.microsoft.com/en-us/dotnet/core/tools/dotnet-environment-variables#corehost_trace

host_trace.txt.zip

I executed this using the repro from the initial description:

DOTNET_HOST_TRACEFILE=host_trace.txt DOTNET_HOST_TRACE=1 DOTNET_ROOT=$(pwd)/dotnet ./dotnet/sdk/10.0.100/Roslyn/bincore/csc --help

[agocke]

@AaronRobinsonMSFT can you take a first look? I don’t think we changed anything significant recently so it smells like it might be miscompilation.