Skip to main content

Internal Guide: Memory leak tickets and how to handle them

Updated over a month ago

Issue

The customer reaches out to Support due to memory leak issues.

Applies To

  • All SDKs

Symptoms

First of all, it's important to understand what a memory leak is. Google to the rescue:

Screenshot 2024-07-23 at 14.31.46.png

Most of the time, the customers will report that the Sentry SDK is causing:

  • a "memory leak" or

  • their app to go "out of memory"

Resolution

Step 1 - Make sure the memory leak is actually due to our app

Did the user provide enough information to make it clear that's the Sentry app causing the memory leak, such as screenshots of a AWS logs, or the error?

If not, ask some probing questions to verify.

Step 2 - Gather as much information as you can (you can ask this information as part of Step 1 to save time):

  • Environment the app if running (framework, version, OS)

  • SDK & version

  • SDK Init

  • Logs or any other information showing the leak.

Step 3 - GitHub ticket

Check if there's already a Github ticket filed for that environment. If not, create one.

If you are not sure, or have questions before filing a GitHub ticket, feel free to post on #discuss-sdks

What's important to note here is that it's better to escalate memory leaks earlier than later.

Did this answer your question?