A small leak can sink a great ship
summary
Memory leaks cause freezes and OOM crashes; heap dumps freeze the app and LeakCanary triggers them when retained-object counts exceed a threshold (default 5 visible / 1 background). The workflow uses LeakCanary 2 + Shark to detect and group leaks, a one-line debug install, test assertions to fail CI, and uploads heap-analysis results as non‑fatal events to Firebase Crashlytics (with code‑owner tagging, velocity alerts and Jira/webhook hooks). The new analyzer uses 10x less memory.
AI-written summary · about
chapters (18)
- 0:00Start
- 3:14Android Memory Structure
- 4:10Stack Memory
- 5:20Heap Memory
- 6:31Garbage Collector
- 6:59Memory Leaks
- 10:49Retained Object Detection
- 13:09Dumping Heap
- 13:39Analyzing Heap
- 14:37Leak Trace
- 19:01Leak Canary 2 with Test Rules
- 21:44Developer Strategy
- 22:52Leak Canary 2 Implemetation
- 23:12Leak Canary 2 Listener
- 23:50Leak Canary 2 Config
- 24:01Leak Canary Upload Service
- 28:36Leak Data + Firebase Crashlytics
- 31:33Prevention is better than cure!
related talks
31mA Small Leak Can Sink A Great Ship
37mLeakCanary, then what? Nuking Nasty Memory Leaks
37mRoot causing memory growth with LeakCanary 3
39mLeakCanary 2: Leaner, Better, Faster, Kotliner!
47mLeakCanary, and Then? Unraveling Android Memory Leaks
37mUniversal heap trimming with LeakCanary 3
25mMemory leaks on Android: lessons learned and methodology
23mReducing memory footprint of your app - what LeakCanary is not telling you about