Stack overflow caused by SqlConfigurableRetryLogicLoader.Defaul_resolving

[sfiruch]

Describe the bug

I have an Blazor web app on .NET 7, using EF and Microsoft.Data.SqlClient 5.0.2. The web app was running fine for several months. It crashed this morning, with the following exception:

Stack overflow.
   at System.RuntimeMethodHandle._GetCurrentMethod(System.Threading.StackCrawlMark ByRef)
   at System.Reflection.MethodBase.GetCurrentMethod()
   at Microsoft.Data.SqlClient.SqlConfigurableRetryLogicLoader.Default_Resolving(System.Runtime.Loader.AssemblyLoadContext, System.Reflection.AssemblyName)
   at System.Runtime.Loader.AssemblyLoadContext.GetFirstResolvedAssemblyFromResolvingEvent(System.Reflection.AssemblyName)
   at System.Runtime.Loader.AssemblyLoadContext.ResolveUsingEvent(System.Reflection.AssemblyName)
   at System.Runtime.Loader.AssemblyLoadContext.ResolveUsingResolvingEvent(IntPtr, System.Reflection.AssemblyName)
   at Microsoft.Data.SqlClient.SqlConfigurableRetryLogicLoader.MakeFullPath(System.String, System.String, System.String)
   at Microsoft.Data.SqlClient.SqlConfigurableRetryLogicLoader.Default_Resolving(System.Runtime.Loader.AssemblyLoadContext, System.Reflection.AssemblyName)
   at System.Runtime.Loader.AssemblyLoadContext.GetFirstResolvedAssemblyFromResolvingEvent(System.Reflection.AssemblyName)
   at System.Runtime.Loader.AssemblyLoadContext.ResolveUsingEvent(System.Reflection.AssemblyName)
   at System.Runtime.Loader.AssemblyLoadContext.ResolveUsingResolvingEvent(IntPtr, System.Reflection.AssemblyName)
   at Microsoft.Data.SqlClient.SqlConfigurableRetryLogicLoader.MakeFullPath(System.String, System.String, System.String)
   at Microsoft.Data.SqlClient.SqlConfigurableRetryLogicLoader.Default_Resolving(System.Runtime.Loader.AssemblyLoadContext, System.Reflection.AssemblyName)
   at System.Runtime.Loader.AssemblyLoadContext.GetFirstResolvedAssemblyFromResolvingEvent(System.Reflection.AssemblyName)
   at System.Runtime.Loader.AssemblyLoadContext.ResolveUsingEvent(System.Reflection.AssemblyName)
   at System.Runtime.Loader.AssemblyLoadContext.ResolveUsingResolvingEvent(IntPtr, System.Reflection.AssemblyName)
   at Microsoft.Data.SqlClient.SqlConfigurableRetryLogicLoader.MakeFullPath(System.String, System.String, System.String)
   at Microsoft.Data.SqlClient.SqlConfigurableRetryLogicLoader.Default_Resolving(System.Runtime.Loader.AssemblyLoadContext, System.Reflection.AssemblyName)
   at System.Runtime.Loader.AssemblyLoadContext.GetFirstResolvedAssemblyFromResolvingEvent(System.Reflection.AssemblyName)
   at System.Runtime.Loader.AssemblyLoadContext.ResolveUsingEvent(System.Reflection.AssemblyName)
   at System.Runtime.Loader.AssemblyLoadContext.ResolveUsingResolvingEvent(IntPtr, System.Reflection.AssemblyName)
   at Microsoft.Data.SqlClient.SqlConfigurableRetryLogicLoader.MakeFullPath(System.String, System.String, System.String)
   at Microsoft.Data.SqlClient.SqlConfigurableRetryLogicLoader.Default_Resolving(System.Runtime.Loader.AssemblyLoadContext, System.Reflection.AssemblyName)
   at System.Runtime.Loader.AssemblyLoadContext.GetFirstResolvedAssemblyFromResolvingEvent(System.Reflection.AssemblyName)
   at System.Runtime.Loader.AssemblyLoadContext.ResolveUsingEvent(System.Reflection.AssemblyName)
   at System.Runtime.Loader.AssemblyLoadContext.ResolveUsingResolvingEvent(IntPtr, System.Reflection.AssemblyName)
...

To reproduce

Have restarted the app, but was not (yet) successful to repro.

Didn't configure any special options, environment variables, etc. AFAIK. This is the connection string (password etc. changed):
Data Source=tcp:super-secret.database.windows.net,1433;Initial Catalog=mywebsite.com;Integrated Security=False;Persist Security Info=False;User ID=super-secret;Password=123456;Encrypt=True

Further technical details

Microsoft.Data.SqlClient version: 5.0.2
.NET target: 7.0
SQL Server version: Azure SQL
Operating system: Ubuntu 20.04.3 LTS

[ErikEJ]

Have you tried 5.1.2 ?

[sfiruch]

Have you tried 5.1.2 ?

Yes, this is the version that's running now.

I didn't notice any changes in the relevant areas (but didn't look very hard). It'll take months to determine whether the problem is fixed. I had hoped that the person working in this area could make sense of the stack overflow immediately.

[arellegue]

@deiruch, before I can begin investigation, may I ask for a repro code, please? I would like to know how SqlConfigurableRetryLogic is configured in your code.

[sfiruch]

@deiruch, before I can begin investigation, may I ask for a repro code, please? I would like to know how SqlConfigurableRetryLogic is configured in your code.

I only have a full website that showed the behavior after running for several months. The source code is private. Should I share the code with you?

The code is not special at all: It's using EF Core 7.0.13.0 with default options for database access. I didn't configure SqlConfigurableRetryLogic manually.

[arellegue]

@deiruch, could you at least provide information such as:

1. App.config
2. appsettings.json
3. In your DbContext class, the content of OnConfiguring(DbContextOptionsBuilder optionsBuilder)

[sfiruch]

Sure, I'm happy to! But I fear there's nothing of interest in there. It's really just using defaults.

App.config

Does not exist

appsettings.json

{
  "Logging": {
    "LogLevel": {
      "Default": "Information",
      "Microsoft.AspNetCore": "Warning"
    }
  },
  "EmailSender": {
    "Host": "smtp-pulse.com",
    "Port": 2525,
    "EnableSSL": false,
    "UserName": "123",
    "Password": "123",
    "From": "123@secret.com"
  },
  "AllowedHosts": "*",
  "LettuceEncrypt": {
    "AcceptTermsOfService": true,
    "DomainNames": [ "secret.com" ],
    "EmailAddress": "123@secret.com",
    "AllowedChallengeTypes": "Http01",
    "UseStagingServer": false
  },
  "https_port": 443,
  "Kestrel": {
    "Endpoints": {
      "Http": {
        "Url": "http://*:80"
      },
      "Https": {
        "Url": "https://*:443"
      }
    }
  }
}

OnConfiguring

    protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
#warning To protect potentially sensitive information in your connection string, you should move it out of source code. You can avoid scaffolding the connection string by using the Name= syntax to read it from configuration - see https://go.microsoft.com/fwlink/?linkid=2131148. For more guidance on storing connection strings, see http://go.microsoft.com/fwlink/?LinkId=723263.
        => optionsBuilder.UseSqlServer("Data Source=tcp:secret.database.windows.net,1433;Initial Catalog=secret;Integrated Security=False;Persist Security Info=False;User ID=secret;Password=123;Encrypt=True");