Memory Terminations
Learn how Luciq reports Android 17 memory terminations, when the system kills your app for going over its memory limit, and what data each report includes.
Starting with Android 17, Android sets a memory limit for every app. When your app goes over its limit, the system kills it. There is no crash and no stack trace, so your users only see the app close, and you had no way to know it happened.
Luciq detects these kills automatically and reports them as Memory Terminations. You can find the screens that use too much memory and fix them before they drive users away.
What does a Memory Termination look like?
User opened the App
The App kept using more memory, for example while loading large images
Android killed the App because it went over its memory limit
User opened the App again
How are Memory Terminations detected?
Android records why each app process ended. The next time the user opens your app, the Luciq SDK reads these records. If the previous session ended because the app went over its memory limit, the SDK reports a Memory Termination for that session.
This means a Memory Termination reaches your dashboard after the user opens the app again. The SDK detects kills that happen while the app is in the foreground and while it is in the background.
How can I see Memory Terminations on the dashboard?
Memory Terminations have their own page in the dashboard sidebar, under Issues → Memory terminations. They don't appear in the Crashes list.
Similar terminations are grouped together:
If the app was in the foreground, they are grouped by the Activity the user was on. If the Activity is unknown, they are grouped under N/A.
If the app was in the background, they are grouped under Background.
If your app uses a single Activity, for example a Jetpack Compose app, all of its foreground kills land in one group.
What data is available in a Memory Termination:
Patterns to highlight which subset of users has had the highest number of Memory Terminations.
Occurrences view, where you can view every occurrence and what led to it.
Occurrences include the following debugging data:
Metadata of the device
The screen the user was on and whether the app was in the foreground or the background
Memory details reported by Android, when available: the termination sub-reason, and the PSS and RSS memory of the app
Repro steps which is a visual step-by-step reproduction of the session of the user, screen by screen and interaction by interaction on the app up until Android killed it.
Logs section including console logs and network logs for all API calls that were made during the session.
How are Memory Terminations different from crashes?
No stack trace. Android kills the app without a crash, so there is no stack trace to group by. This is why foreground Memory Terminations are grouped by Activity, and background ones under Background.
No effect on your stability scores. Memory Terminations are a new metric, so they don't count toward your crash-free sessions, crash-free users, or Frustration-Free Sessions score. They are not counted as Force Restarts either.
No new-crash emails or rule actions. Like Force Restarts, a new Memory Termination doesn't send a new-crash email and doesn't run your crash rules.
Current limitations
Memory Terminations are not supported in alerts yet.
Memory Terminations are not available through the Luciq MCP crash tools yet.
Memory Terminations are reported for Android only. For memory issues on iOS, see OOM in Crash Reporting Types.
Memory Terminations show you a problem that was invisible before. With the screen, the app state, and the memory details of every kill, you can find the parts of your app that use too much memory and fix them early.
Last updated