Problem with runtime async in .NET 11 RC1: unexpectedly larger binary size #133954

Activity

1. github-actions

   added

   area-CodeGen-coreclrCLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMICLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI

   on Sep 15, 2026
2. dotnet-policy-service

   added

   untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

   on Sep 15, 2026
3. dotnet-policy-service commented on Sep 15, 2026

   

   dotnet-policy-serviceBot

   on Sep 15, 2026 – with Dotnet Policy Service

   Contributor

   More actions

   Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
   See info in area-owners.md if you want to be subscribed.
4. tannergooding commented on Sep 15, 2026

   

   tannergooding

   on Sep 15, 2026

   Last edited by tannergooding

   Member

   More actions

   There was some more discussion on Discord and notably it looked like various things like TimeZoneInfo were being indirectly rooted

   Paths like Main->NamedPipeServerStream->SR.get_InvalidOperation_PipeAlreadyConnected->ResourceManager->ResourceReader.LoadObjectV2->DateTime.FromBinary->TimeZoneInfo.cctor for example

   It might be more general cases of the static constructor trimming that got done for #132576 and which is included for RC2 (but not RC1)

   👍React with 👍1Reacted by Violet Hansen
5. jakobbotsch

   added

   area-NativeAOT-coreclr

   on Sep 15, 2026
6. github-project-automation

   added this to AppModelon Sep 15, 2026
7. jakobbotsch

   removed

   area-CodeGen-coreclrCLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMICLR JIT compiler in src/coreclr/src/jit and related components such as SuperPMI

   untriagedNew issue has not been triaged by the area ownerNew issue has not been triaged by the area owner

   on Sep 15, 2026
8. dotnet-policy-service commented on Sep 15, 2026

   

   dotnet-policy-serviceBot

   on Sep 15, 2026 – with Dotnet Policy Service

   Contributor

   More actions

   Tagging subscribers to this area: @agocke, @dotnet/ilc-contrib
   See info in area-owners.md if you want to be subscribed.
9. tannergooding commented on Sep 15, 2026

   

   tannergooding

   on Sep 15, 2026

   Member

   More actions

   with a different standalone sample, I see the regression too
   notably RC2 is smaller than RC1, but the gap between runtime-async=off vs on is even larger (bigger regression)

   looks to generally be because the substituted IL only works with EcmaMethodIL and so it fails to fold the resource accesses because NativeAotILProvider.AsyncMethodIL fails that check

   so we basically get this and it stays rooted due to not folding

   Main <AsyncCallable>
     -> WaitForConnectionCoreAsync <AsyncCallable>
     -> SR.get_InvalidOperation_PipeAlreadyConnected
     -> ResourceManager / ResourceReader._LoadObjectV2
     -> DateTime.FromBinary
     -> TimeZoneInfo.Local / .cctor
   

   👍React with 👍1Reacted by Violet Hansen
10. jakobbotsch

    closed this as completedin #133970on Sep 16, 2026
11. JulieLeeMSFT

    added a commit that references this issue on Sep 17, 2026

    [release/11.0] Fix NativeAOT resource string inlining for async IL (#…

    ...

    be70323
12. github-actions

    locked and limited conversation to collaborators on Oct 17, 2026