Repository navigation
Memory Issues in HostedService #4685
Description
Package
Sentry.AspNetCore
Sentry.OpenTelemetry
.NET Flavor
.NET Core
.NET Version
9.0.111
OS
Linux
OS Version
Debian 12 (official aspnetcore docker image)
Development Environment
Rider 2024 (Windows)
SDK Version
5.16.0
Self-Hosted Sentry Version
No response
Workload Versions
aspire 8.2.2/8.0.100 SDK 9.0.100
UseSentry or SentrySdk.Init call
builder.WebHost.UseSentry(options =>
{
//DSN from appsettings
options.UseOpenTelemetry();
options.SendDefaultPii = true;
options.MaxRequestBodySize = RequestSize.Always;
options.MinimumBreadcrumbLevel = LogLevel.Debug;
options.MinimumEventLevel = LogLevel.Error;
options.AttachStacktrace = true;
options.TracesSampleRate = 0.0;
options.Environment = builder.Environment.EnvironmentName;
options.AddExceptionFilterForType<OperationCanceledException>();
options.AddExceptionFilterForType<KustoClientRequestCanceledByUserException>();
});Steps to Reproduce
- Create a WebApplicationBuilder
- Add a hosted Service (BackgroundService) in our case
- Run that service in a loop (while (!stoppingToken.IsCancellationRequested)...)
- Watch the memory for a prolonged time
Expected Result
The memory keeps stable over a longer period
Actual Result
tldr:
memory spikes that results in System.OutOfMemory exeptions
Longer version:
We've introduced Sentry in 4 of our backend services a few weeks ago. Right after deploying those services to our Azure container background, we've noticed some OutOfMemory Exceptions on two of our services. Both services have BackgroundServices where the exceptions occur. Both BackgroundServices start a loop for the entire lifetime of the service, periodically checking with an Azure Queue Client for updates.
We've tried a few things, but in the end kinda resolved the issue with a manual GC.Collect() after each run of the loop and the memory level went back to normal (as you can see in the screenshot)
Metadata
Metadata
Assignees
Projects
- Status
- Status
Activity
linear commentedon Oct 31, 2025
NET-513
jamescrosswell commentedon Nov 2, 2025
Hey @joshua211 ,
You could try capturing a heap dump, to see what's eating all the memory:
That functionality is still experimental. The main issue with it is that Sentry can't handle really large files, but if it's just in your sample app and the dump is reasonably simple then it should work.
jamescrosswell commentedon Nov 17, 2025
@joshua211 could it be related to this?
That has been fixed in the upcoming version 6 release. We'll get it back ported to v5 as soon as possible as well.
joshua211 commentedon Apr 15, 2026
Hello,
sorry it took us some time to look into this.
We upgraded our Sentry version to 6, but the memory leak still persists.
jamescrosswell commentedon Apr 15, 2026
@joshua211 it may well be related to this:
This will be includede in the 6.4.0 release:
jamescrosswell commentedon Apr 17, 2026
@joshua211 version 6.4.0 is now available. Would be great to check/confirm whether this resolves the issue for you. If not, we'd need to do some more digging.
jamescrosswell commentedon May 4, 2026
I'll close this issue for now. If you've still got problems after upgrading to the latest version of Sentry, feel free to reopen.