- [August 19, 2026] → Android Developers Blog — publication date of Google’s per-app memory limits guidance
Open Crashlytics on a phone with 4GB of RAM and you may soon see a string buried in the exit data: MemoryLimiter:AnonSwap. It is Android’s way of telling a developer that the system forced their app’s memory into compressed swap, then possibly killed the process.
The signal is new, and it points to a broader shift. Google’s Android team published the guidance on August 19, 2026 Android Developers Blog, explaining that per-app memory limits first shipped in Android 17 on Pixel devices and will now spread across manufacturers over the coming year.
The caps will reach phones with 4GB to 16GB+ of RAM. Cross a device’s limit and Android reacts in stages.
Why Google is tightening the cap now
The push comes from hardware economics, not a sudden appetite for control. Memory prices have pushed device makers to hold or shrink physical RAM even as users expect the same smooth experience. One greedy app can drag the whole device down.
Google explained the reasoning: “The limits protect the overall user experience from applications using excess memory and causing system-wide slowdowns.”
But protection has a cost for developers. When an app hits its budget, the system first pushes pages into zRAM, a compressed slice of RAM. Compression adds CPU work, which shows up as UI jank. Keep climbing and the process is terminated outright.
How the throttling actually feels
Android does not hide the failure. Call getDescription() inside ApplicationExitInfo and a limit-driven exit reports REASON_OTHER with the description string “MemoryLimiter:AnonSwap”. Developers can also capture heap dumps automatically when the cap is hit using TRIGGER_TYPE_ANOMALY.
Crashlytics 20.1.0 adds debug data so teams can separate ordinary Out-Of-Memory crashes from memory-limiter kills Android Developers Blog. Google’s Play Console surfaces the same pressure at population scale through Android vitals metrics like Memory Usage (RSS plus swap) and Bitmap Memory Usage.
The optimization work itself leans on Android’s Jetpack libraries and the memory best practices Google publishes for the platform, including the Memory Limiter adb commands for testing tighter RAM configs and separate guidance for games and complex multimedia apps Android developer resources.
What developers should check first
Start with the field signals rather than a profiler. If Crashlytics shows MemoryLimiter:AnonSwap exits, the app is already being throttled on real devices. The ProfilingManager API, added in Android 15 (API level 35), lets an app pull heap dumps and heap profiles from production phones on TRIGGER_TYPE_OOM and TRIGGER_TYPE_ANOMALY.
App makers already juggling new platform rules have more compliance ahead. Google now requires developer verification across seven Android app stores zBrandco, a separate mandate that lands on top of the memory work.
The memory limits are not a one-time setting. As RAM configurations keep shifting, the apps that survive are the ones whose teams watch the swap counter before users feel the jank.
