SentryTracing crashes ASP.NET web apps on .NET 10

[kanadaj]

Package

Sentry

.NET Flavor

.NET

.NET Version

10.0.0

OS

Any (not platform specific)

OS Version

No response

Development Environment

Other

SDK Version

5.14.1

Self-Hosted Sentry Version

No response

Workload Versions

Doesn't matter, blank test project works to showcase

UseSentry or SentrySdk.Init call

var builder = WebApplication.CreateBuilder(args);

builder.WebHost.UseSentry(x => ConfigureSentry(x, builder.Environment));

static void ConfigureSentry(SentryAspNetCoreOptions options, IWebHostEnvironment env)
{
    options.Dsn = "https://abc123@sentry.io.com/2";
    options.AutoRegisterTracing = true;
}

Steps to Reproduce

1. Clone https://github.com/Mitch528/sentry-crash-repro
2. Run dotnet run
3. Open the home page
4. Observe that the app crashes

Expected Result

The app shouldn't crash, the error page should be shown

Actual Result

CLI process terminates. Disabling options.AutoRegisterTracing = true; removes the issue. Not having await before the crash also removes the issue so the async pipeline might also be related.

We also believe that dotnet/runtime#121578 might be related to this issue.

[linear]

NET-527

[jamescrosswell]

Thanks @kanadaj - version 5 of the Sentry SDK won't work with .NET 10.

6.0-preview2 is already available (which does).

We're just in the process of preparing a 6.0-rc release as well... That should be available in the next couple of days.

[kanadaj]

@jamescrosswell Still seems to crash on 6.0-preview2; might need to reload the exception page a couple times to see it crash

[jamescrosswell]

@kanadaj I can't reproduce... I did comment out this line (since the app would obviously crash with that line included).

btw: It's not necessary to set options.AutoRegisterTracing = true; since that's the default value for the property.

[kanadaj]

@kanadaj I can't reproduce... I did comment out this line (since the app would obviously crash with that line included).

btw: It's not necessary to set options.AutoRegisterTracing = true; since that's the default value for the property.

It's ASP.NET Core, exceptions on Actions aren't meant to crash the entire app, it should just result in an error page. That's the whole issue. The Sentry middleware is somehow causing exceptions to bubble up to the runtime, bypassing the normal ASP.NET error page middleware, crashing the entire app.

[jamescrosswell]

Ahhh, I see what you're saying now.

Will do a bit of digging...