Android 17 is getting stricter with apps that use too much memory, and Google would rather make one app suffer than let it drag down the rest of your phone.
Google says Android 17 introduces per-app memory limits based on a device’s total RAM. The feature is designed to catch extreme memory use before it starts causing UI stuttering or draining more battery. Apps that keep pushing past their budget can eventually be terminated.
What happens when an app goes too far
Android 17 doesn’t give every app the same RAM allowance. Google says the thresholds are deliberately conservative, so ordinary app sessions should rarely run into them.
When an app does cross its ceiling, Android can start reclaiming memory instead of immediately squeezing other processes. If its memory use keeps climbing, Android 17 can eventually terminate the offending process.
That gives Android a way to contain the problem before the rest of the phone has to deal with it.
How much RAM can an app use
The allowance depends on the device and whether the process is visible. Google’s AOSP documentation shows that an 8GB device, for example, gives a visible process a 5GB limit, while a non-visible process gets 3GB.
Going over that threshold doesn’t automatically kill the app. Android can first reclaim memory and push inactive data into compressed zRAM, which may make the offending app slower while keeping it alive.
Termination comes later in more extreme cases, such as a memory leak that keeps allocating resources after available swap space is exhausted. The app takes the hit rather than forcing Android to clear out other useful processes first.
What you’ll notice on your phone
Ideally, you won’t notice much during normal use. Google expects ordinary app sessions to stay comfortably below these thresholds.
The rules also apply broadly. AOSP says preinstalled apps aren’t exempt, and developers don’t get an allowlist that lets their apps sidestep the system.
So if an app suddenly slows down or closes under heavy memory pressure, Android 17 may be doing exactly what it was designed to do. The phone keeps running, while the app causing the problem gets dealt with first.
