Android memory and games
summary
Android games run without a fixed RAM budget because the system keeps RAM full for app switching, uses zRAM compressed swap, and kills processes via LMK when thresholds hit; a test app still allocates 4.1 GB on a 4 GB device because much is compressed. Q adds pressure stall info, RSS trace points and more reliable onTrimMemory warnings; use Perfetto (long traces, RSS) and Heapprofd for low-overhead heap tracing, check adb dumpsys meminfo and bugreport, throttle allocations and evict assets to avoid thrashing and kills.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:15Overview
- 1:01Problems with memory
- 2:40How much memory is available
- 4:24Android memory philosophy
- 6:48Memory types
- 9:13Memory reclaims
- 15:19Summary
- 15:51Respond to longterm memory
- 20:31Be flexible
- 25:16PSS vs RSS
- 26:51Perfetto
- 31:11Heap Property
- 32:13Bug Report
- 34:16Conclusion
related talks
07mAndroid memory tools and best practices
39mUnderstanding Android memory usage
38mOptimize your app performance for the next generation of Android
46mDeveloping for Android: the Naughty Bits- 38mOptimize your app performance for the next generation of Android
40m640K ought to be enough for anyone
53mMemory on Android, Leaks and OOM
49mKeynote: Android Development