android-bug-hunting-lifecycle-leak-hunter

To detect Android memory leaks, this Skill applies static analysis to your Kotlin and Java source files, identifying problematic singleton references and long-lived inner classes holding outer references. It flags patterns causing leaks in Activities, Fragments, Services, and Views to improve app stability.

Memory bloat after configuration changes is often caused by lifecycle violations and improper resource handling. This Skill analyzes your app code to identify root causes like missing unregister calls for listeners and invalid view binding access during lifecycle transitions.

Finding unregistered listeners involves scanning for lifecycle management issues where resources are not properly released. This Skill performs static analysis on your source files to flag listeners that are not unregistered, alongside view binding misuse and singleton reference violations.

Yes, static analysis can find view binding misuse in Kotlin and Java source files. This Skill scans your provided code to flag invalid view binding access and other lifecycle violations, helping you resolve memory leaks and improve memory efficiency.

The best way to check for singleton reference leaks is using static analysis on your Android source code. This Skill evaluates your Kotlin and Java files to flag problematic singleton references and long-lived inner classes holding outer references that lead to memory leaks.