Replies: 2 comments 4 replies
-
Hm, normally those Are you able to simulate the load etc. required to observe this with Diagnostic logging turned on? So initialize Sentry with:
I'm wondering if there are any errors in the |
Beta Was this translation helpful? Give feedback.
-
Thanks heaps @danpaul88 ! I was able to reproduce this locally and I've created an issue to track this: Now to fix it (hopefully)... |
Beta Was this translation helpful? Give feedback.
-
I'm unsure if this is a bug or an artifact of how I'm using Sentry, so rather than creating an issue I though I'd check to see if anyone has come across this before...
When using
Sentry.OpenTelemetry
(v3.41.3) withOpenTelemetry.Instrumentation.AspNetCore
(v1.6.00-beta.3) andOpenTelemetry.Instrumentation.Http
(v1.6.00-beta.3) I'm seeing what appears to be a memory leak in theSentrySpanProcessor
SentrySpanProcessor
is holding ~700mb of the ~900mb of memory in this service, which was idle at the time of the memory dump and had been running for ~35 days, which suggests it's slowly accumulating more and more spans inSentrySpanProcessor._map
.Looking at a random selection of the spans, they all seem to be
System.Net.Http.HttpRequestOut
spansDoes anyone have any ideas why we're accumulating so much stuff in the
SentrySpanProcessor
and whether there's anything we can do to clear it out, short of periodically restarting the services to reclaim memory (not ideal! )Beta Was this translation helpful? Give feedback.
All reactions