What problem does it solve? Android apps often suffer from memory leaks and OOM crashes caused by retained Activities, Fragments, Views, listeners, and coroutines. This Skill provides a structured workflow to interpret LeakCanary reports, walk retention chains, classify the leak type, and recommend a fix that preserves behavior. ## Core Features & Use Cases - Retention Path Analysis: Trace strong reference chains to find the first suspicious owner, whether static, singleton, callback, coroutine, or observer. - Leak Classification: Categorize leaks into common buckets such as Fragment view binding leaks, adapter-held Activity references, unremoved listeners, and unbounded caches. - Fix and Validation Guidance: Recommend lifecycle-correct fixes (clearing bindings in onDestroyView, unregistering listeners, canceling screen-scoped jobs) plus LeakCanary recheck and memory profiler validation steps. - Use Case: You receive a LeakCanary report showing a retained Activity after repeated navigation. Use this Skill to walk the retention path, identify a singleton holding a Context reference, and get a fix with verification steps. ## Quick Start Analyze this LeakCanary report and the related source files to identify the leak owner and recommend a fix with validation steps.
