How to debug a high low memory kill rate? | Sentry Community | Page 1

next gust Jun 20, 2025, 5:10 PM

#

Hi in our play store console, we are seeing a high low memory kill rate for a current release. We are trying to diagnose where in the app this is happening, but are not seeing the corresponding error log in Sentry. Do these kills get logged? Is there a way to find them?

#

@vocal night as an FYI

golden brook Jun 23, 2025, 10:35 AM

#

hi, no we don't support that yet, it's pretty fresh in the play vitals too. It's possible to get those from AppExitInfo, and we have an issue for general reporting of AppExitInfo reasons, so I imagine this will be possible once we start doing that.

GitHub

Report app exit reasons · Issue #3958 · getsentry/sentry-java

Problem Statement Having more context on ANR's is always required Solution Brainstorm https://developer.android.com/reference/android/app/ApplicationExitInfo#REASON_EXCESSIVE_RESOURCE_USAGE ┆Is...

Android Developers

ApplicationExitInfo | API reference | Android Developers

#

as for the reasons why is it happening I guess you could make a correlation based on the OutOfMemoryErrors in Sentry, but they are also lacking. We have an issue to use LeakCanary to improve that

GitHub

Integrate LeakCanary for production OOM/Leaks monitoring · Issue #...

Description LeakCanary has a whole section on how to integrate heap analysis with bugsnag https://square.github.io/leakcanary/leakcanary-for-releases/. We could do something similar and either send...

next gust Jun 26, 2025, 3:48 PM

#

Thanks! This is helpful.

next gust Jun 27, 2025, 5:05 PM

#

Similarly we have issues with "The OS watchdog terminated your app, possibly because it overused RAM." - which are similarly difficult to debug. I imagine they are related.

golden brook Jun 30, 2025, 8:08 AM

#

that's on iOS you mean right?

next gust Aug 14, 2025, 5:43 PM

#

yes we are a react native app so I assume these are part of the same issue

#How to debug a high low memory kill rate?