Tons of OOM. Metrics API could be the cause?

[bruno-garcia]

Groups pretty badly. Should it all group together? Probably not but not sure how to improve this

https://sentry.sentry.io/issues/?project=1886021&query=is%3Aunresolved+issue.priority%3A%5Bhigh%2C+medium%5D+OutOfMemory&referrer=issue-list&statsPeriod=7d

Relates to:

• Improve OutOfMemory insight sentry-dotnet#3315

fyi @bitsandfoxes @jamescrosswell

[bruno-garcia]

Looks like it started after the last release:

https://sentry.sentry.io/discover/homepage/?field=title&field=event.type&field=project&field=user.display&field=timestamp&name=All+Events&project=1886021&query=message%3AOutOfMemory&sort=-timestamp&statsPeriod=90d&yAxis=count%28%29

90 days

30 days

[jamescrosswell]

https://sentry.sentry.io/issues/?project=1886021&query=is%3Aunresolved+issue.priority%3A%5Bhigh%2C+medium%5D+OutOfMemory&referrer=issue-list&statsPeriod=7d

I don't seem to have access to that project. It requires login with Google and only allows certain domains, so assume it's Sentry employees only.

The last release included these two changes - I can't see how either of them would cause an OOM exception though:

• Fixed normalization for metric tag values sentry-dotnet#3281
• Added Metrics rate limits sentry-dotnet#3276

[bruno-garcia]

I gotta bump the version here and release

[bruno-garcia]

Might be fixed. There was the profiling mem leak fixed. And metrics is gone. Server also got more ram as it was getting over the limit often.

[stephanie-anderson]

Why was this issue closed?

This issue hasn't been touched recently and no longer seems relevant.
Hence, we're closing it to maintain a clean and transparent backlog.

Please feel free to leave a comment if you think this issue should be reopened.