LeakCanary, then what? Nuking Nasty Memory Leaks
summary
LeakCanary runs in apps to capture leak traces, then he builds an uploader that fakes crashes into a crash reporter so leaks get grouped and counted; heap dumps upload to Slack for deep inspection. Analysis uses heap dumps opened in YourKit or MAT to find the shortest path to GC roots. Concrete fixes found: unregister application lifecycle callbacks and remove runnables from View/RunQueue (support‑lib keeps a Runnable that can hold an entire view hierarchy for ~30 minutes), and a Picasso cancel bug where code cancels requests on a different Picasso instance.
AI-written summary · about
chapters (5)
related talks
33mNuking Nasty Memory Leaks
47mLeakCanary, and Then? Unraveling Android Memory Leaks
31mA Small Leak Can Sink A Great Ship
35mA small leak can sink a great ship
49mPokeLeaks: Gotta Catch 'em All
37mRoot causing memory growth with LeakCanary 3
PokeLeaks: Gotta Catch 'em All
39mLeakCanary 2: Leaner, Better, Faster, Kotliner!