Memory leak with unclosed span in opentelemetry integration

[vanchaxy]

Memory leak with unclosed span in opentelemetry integration

[vanchaxy]

That's a very controversial solution. At least, make SPAN_MAX_TIME_OPEN_MINUTES configurable. Our system has a lot of long-running jobs that are longer than 10 minutes. I think the proper solution will be to create weak references to otel spans and remove sentry spans only if otel spans were deleted.

[sentrivana]

Thanks for the report @vanchaxy, putting this in our backlog.

[Undefined-User]

Same problem, docker containing the flask process crashes about once an hour due to memory overflow when no heavy tasks are performed.

[bruno-garcia]

isn't this a p0? it's def a p0 in .NET

[DanielNoord]

@antonpirker Is there any interest in making this configurable? I have spend countless hours trying to understand why my OpenTelemetry spans were missing their root spans and it now turns out it is because a hidden global constant.