Android recyclerview 我可以从LeakCanary v2.0-beta-3获得诊断此泄漏跟踪的帮助吗?
这是我从泄漏的金丝雀那里得到的全部泄漏痕迹。这似乎来自一个Android recyclerview 我可以从LeakCanary v2.0-beta-3获得诊断此泄漏跟踪的帮助吗?,android-recyclerview,memory-leaks,leakcanary,Android Recyclerview,Memory Leaks,Leakcanary,这是我从泄漏的金丝雀那里得到的全部泄漏痕迹。这似乎来自一个片段,其中包含一个谷歌地图。我很困惑,因为GoogleMap片段中没有RecyclerView。GoogleMap片段是Android应用程序中三个片段中的一个。在其他两个中使用了RecyclerView LibraryLeak(className=androidx.constraintlayout.widget.ConstraintLayout, leakTrace= ┬ ├─ android.view.inputmethod.In
片段
,其中包含一个谷歌地图
。我很困惑,因为GoogleMap片段中没有RecyclerView
。GoogleMap片段
是Android
应用程序中三个片段中的一个。在其他两个中使用了RecyclerView
LibraryLeak(className=androidx.constraintlayout.widget.ConstraintLayout, leakTrace=
┬
├─ android.view.inputmethod.InputMethodManager
│ Leaking: NO (InputMethodManager↓ is not leaking and a class is never leaking)
│ GC Root: System class
│ ↓ static InputMethodManager.sInstance
├─ android.view.inputmethod.InputMethodManager
│ Leaking: NO (InputMethodManager is a singleton)
│ ↓ InputMethodManager.mNextServedView
│ ~~~~~~~~~~~~~~~
├─ androidx.recyclerview.widget.RecyclerView
│ Leaking: YES (View detached and has parent)
│ mContext instance of com.example.surfbait30.MainActivity with mDestroyed = false
│ View#mParent is set
│ View#mAttachInfo is null (view detached)
│ View.mWindowAttachCount = 1
│ ↓ RecyclerView.mParent
├─ android.widget.LinearLayout
│ Leaking: YES (RecyclerView↑ is leaking and View detached and has parent)
│ mContext instance of com.example.surfbait30.MainActivity with mDestroyed = false
│ View#mParent is set
│ View#mAttachInfo is null (view detached)
│ View.mWindowAttachCount = 1
│ ↓ LinearLayout.mParent
╰→ androidx.constraintlayout.widget.ConstraintLayout
Leaking: YES (LinearLayout↑ is leaking and ObjectWatcher was watching this)
mContext instance of com.example.surfbait30.MainActivity with mDestroyed = false
View#mParent is null
View#mAttachInfo is null (view detached)
View.mWindowAttachCount = 1
key = 0fbb38f9-458e-4e79-a784-7e3ca197f5d3
watchDurationMillis = 13927
retainedDurationMillis = 8925
这是一个库泄漏,这意味着它是Android框架中已知的泄漏(input method manager泄漏)。您自己的代码在这里没有任何泄漏