How does LeakCanary detect memory leaks related to destroyed Activities?

LeakCanary detects memory leaks related to destroyed Activities by tracking weak references (WeakReference) to Activity objects. When an Activity is destroyed, LeakCanary checks whether it has been properly removed from memory.

If the weak reference to the Activity does not become null some time after its destruction, it means there are still strong references to it, and the object has not been garbage collected — this indicates a leak.

LeakCanary automatically creates a heap dump and analyzes it to determine the chain of references holding the Activity, helping developers identify the cause of the leak.