blob: 19e042921f3077b9592b6935df2c5b98ed40d160 [file] [log] [blame]
====================================
HEAP ANALYSIS RESULT
====================================
1 APPLICATION LEAKS
References underlined with "~~~" are likely causes.
Learn more at https://squ.re/leaks.
44730 bytes retained by leaking objects
Displaying only 1 leak trace out of 2 with the same signature
Signature: 442f3a7295abb8db4c32672ff17a43941effe5d0
┬───
├─ android.com.java.profilertester.fragment.FragmentHostActivity$1 instance
│ Leaking: NO (FragmentHostActivity↓ is not leaking)
│ this$0 instance of android.com.java.profilertester.fragment.FragmentHostActivity with mDestroyed = false
│ ↓ FragmentHostActivity$1.this$0
├─ android.com.java.profilertester.fragment.FragmentHostActivity instance
│ Leaking: NO (Activity#mDestroyed is false)
│ mApplication instance of android.app.Application
│ mBase instance of androidx.appcompat.view.ContextThemeWrapper
│ ↓ FragmentHostActivity.fragments
│ ~~~~~~~~~
├─ androidx.fragment.app.Fragment[] array
│ Leaking: UNKNOWN
│ Retaining 2.1 kB in 69 objects
│ ↓ Fragment[0]
│ ~~~
╰→ android.com.java.profilertester.fragment.FragmentA instance
​ Leaking: YES (ObjectWatcher was watching this because android.com.java.profilertester.fragment.FragmentA received Fragment#onDestroy() callback. Conflicts with Fragment.mLifecycleRegistry.state is RESUMED)
​ Retaining 42.7 kB in 756 objects
​ key = f349accc-be6b-4f1d-b560-f2e0942a468f
​ watchDurationMillis = 3692
​ retainedDurationMillis = -1
​ key = 68029044-2974-4b30-ad56-840388723a09
​ watchDurationMillis = 4588
​ key = 9bc6c569-2edc-4f82-bf6b-b0d349e6ab40
​ watchDurationMillis = 5728
​ retainedDurationMillis = 722
​ key = 5296c9c7-b2f8-4c6f-8e2c-362f3b3120de
​ watchDurationMillis = 14010
​ retainedDurationMillis = 9009
​ key = 01c3419d-570a-4ad5-8ea7-09a4414b1172
​ watchDurationMillis = 26705
​ retainedDurationMillis = 21702
​ navigateListener instance of android.com.java.profilertester.fragment.FragmentHostActivity with mDestroyed = false
====================================
0 LIBRARY LEAKS
A Library Leak is a leak caused by a known bug in 3rd party code that you do not have control over.
See https://square.github.io/leakcanary/fundamentals-how-leakcanary-works/#4-categorizing-leaks
====================================
0 UNREACHABLE OBJECTS
An unreachable object is still in memory but LeakCanary could not find a strong reference path
from GC roots.
====================================
METADATA
Please include this in bug reports and Stack Overflow questions.
Build.VERSION.SDK_INT: 28
Build.MANUFACTURER: unknown
LeakCanary version: 2.11