PokeLeaks: Gotta Catch 'em All
summary
Hands‑on workshop that injects hidden leaks into the open‑source CatchUp app, adds LeakCanary 2, and reproduces leaks using Android Studio Canary and emulator rotations; LeakCanary reports three distinct retained objects (all from the same root cause), shows colored reference chains in a new UI, and dumps/shareable heapfiles once five retained objects trigger analysis. Fixes demonstrated include removing a duplicate activity lifecycle registration, clearing a fragment registry from its SparseArray, and nulling view‑binding in onDestroyView — fixes remove the reported leaks.
AI-written summary · about
chapters (10)
- 0:00Introduction and setup
- 7:03Adding Leakary to the app
- 15:59Running the app and detecting leaks
- 24:17Analyzing the first memory leak
- 32:31Fixing the first memory leak
- 33:55Leakary notifications and threshold
- 39:58Fragment leaks and lifecycle tracking
- 41:26Common fragment binding leaks
- 46:31Fixing fragment binding leaks
- 47:58Summary and Q&A
related talks
37mLeakCanary, then what? Nuking Nasty Memory Leaks
42mSpeaking of Leaking
47mLeakCanary, and Then? Unraveling Android Memory Leaks
24mUnveiling the Unseen Threat: Demystifying Memory Leaks in Android
33mNuking Nasty Memory Leaks
39mLeakCanary 2: Leaner, Better, Faster, Kotliner!
37mRoot causing memory growth with LeakCanary 3
35mA small leak can sink a great ship