What problem does it solve? Android memory leaks from unregistered listeners, static references, retained Compose state, and runaway coroutines cause OOM crashes and degraded performance, but LeakCanary traces and heap dumps are hard to interpret without a systematic triage process. ## Core Features & Use Cases - Leak Trace Analysis: Reads LeakCanary reference chains from GC root to leaked object to pinpoint the first breakable reference. - Leak Shape Classification: Matches evidence against eight common leak patterns including listener leaks, static context holds, inner-class captures, Handler callbacks, coroutine scope leaks, Compose remember leaks, drawable callbacks, and unbounded Bitmap caches. - False Positive Filtering: Distinguishes real leaks from intentional retention like NavGraph-scoped ViewModels and applicationContext singletons. - Use Case: A developer sees a LeakCanary notification for a leaked Fragment after rotation, pastes the trace, and receives the leak shape, the exact fix (unregister in onDestroyView), and a guardrail test suggestion. ## Quick Start Analyze this LeakCanary trace showing a leaked MainActivity and tell me the leak shape, the fix, and how to prevent it from recurring.
