UnobservedTaskExceptionIntegration could provide a stack trace (but doesn't)

[dbruning]

Package

Sentry.AspNetCore

.NET Flavor

.NET

.NET Version

6.0.11

OS

Windows

SDK Version

3.24.0

Self-Hosted Sentry Version

No response

Steps to Reproduce

1. Cause an UnobservedTaskException in a Blazor event handler, e.g.:

protected void CauseUnobservedTaskException()
	{
		// Task.Run(() => throw new ArgumentException("Test unobserved task exception from Blazor poke page"));
		var task = Task.Factory.StartNew(() =>
		{
			Thread.Sleep(1000); // emulate some calculation
			throw new Exception("Test unobserved task exception from Blazor poke page");
		});

			Thread.Sleep(2000); // emulate some calculation
		task = null;
		GC.Collect();
		GC.WaitForPendingFinalizers();
		GC.Collect();
	}

2. Allow Sentry's default handling to report the error

Expected Result

Issue in Sentry should have a useful stack trace to the cause of the error

Actual Result

Issue in Sentry doesn't have a stack trace.

If I turn off Sentry's handling, e.g.:

webBuilder.UseSentry(sentryOptions =>
{
   sentryOptions.Dsn = ...;
   sentryOptions.DisableUnobservedTaskExceptionCapture();
});

... and add my own code like this:

TaskScheduler.UnobservedTaskException += (sender, e) =>
{
	// Report the inner exception, to get the stack trace
	SentrySdk.CaptureException(e.Exception.InnerException);
};

... then I get a stack trace in Sentry. Could the built-in UnobservedTaskException do this, or something else clever to report the stack trace? Otherwise it's really difficult to debug these issues.

[mattjohnsonpint]

Thanks. I will take a look.

[mattjohnsonpint]

This appears to be a regression, caused by #1922 which fixed #1917. Basically, we had assumed that the aggregate exception was always going to be the source of the stack trace, but in this case the inner exception already has it.

Fix forthcoming.

[dbruning]

Thankyou!