Reducing memory footprint of your app - what LeakCanary is not telling you about
summary
LeakCanary flags no leaks yet Firebase still shows frequent OutOfMemoryError reports; investigation finds screens holding 150+ bitmaps retained because Glide frees resources on destroy not onStop and RecyclerView view pooling preserves large views. Solutions include calling clear/cancel on recycle and onStop, splitting giant list items, and switching bitmap format to RGB_565 to cut bitmap bytes per pixel in half which yields ~50% memory savings on low‑end devices and noticeably reduces OOMs.
AI-written summary · about
chapters (5)
- 0:00Start
- 5:13everything fine?
- 13:27What can be done?
- 16:29decrease image quality!
- 17:42Glide: RGB_565 by default
related talks
41mWays to reduce your app’s memory and storage footprint
35mA small leak can sink a great ship
25mMemory leaks on Android: lessons learned and methodology
47mLeakCanary, and Then? Unraveling Android Memory Leaks
53mMemory on Android, Leaks and OOM
40m640K ought to be enough for anyone
21mAdvanced Memory Management in Flutter
37mLeakCanary, then what? Nuking Nasty Memory Leaks