[疑惑]：是否存在内存泄漏问题

[Mr Huang]

问题描述【必填】

在快速弹出时，提示内存泄漏；
┬───
│ GC Root: Input or output parameters in native code
│
├─ dalvik.system.PathClassLoader instance
│ Leaking: NO (EasyWindow↓ is not leaking and A ClassLoader is never leaking)
│ ↓ ClassLoader.runtimeInternalObjects
├─ java.lang.Object[] array
│ Leaking: NO (EasyWindow↓ is not leaking)
│ ↓ Object[101]
├─ com.hjq.window.EasyWindow class
│ Leaking: NO (a class is never leaking)
│ ↓ static EasyWindow.sWindowInstanceSet
│ ~~~~~~~~~~~~~~~~~~
├─ java.util.ArrayList instance
│ Leaking: UNKNOWN
│ Retaining 152 B in 2 objects
│ ↓ ArrayList[0]
│ ~~~
├─ com.hjq.window.EasyWindow instance
│ Leaking: UNKNOWN
│ Retaining 7.0 kB in 100 objects
│ mContext instance of com.hjq.window.demo.MainActivity with mDestroyed = false
│ ↓ EasyWindow.mDecorView
│ ~~~~~~~~~~
╰→ com.hjq.window.WindowLayout instance
​ Leaking: YES (ObjectWatcher was watching this because com.hjq.window.WindowLayout received
​ View#onDetachedFromWindow() callback)
​ Retaining 6.6 kB in 95 objects
​ key = 19c347dd-c6a0-4f71-bedf-919433656d29
​ watchDurationMillis = 7696
​ retainedDurationMillis = 2695
​ View not part of a window view hierarchy
​ View.mAttachInfo is null (view detached)
​ View.mWindowAttachCount = 1
​ mContext instance of com.hjq.window.demo.MainActivity with mDestroyed = false

METADATA

Build.VERSION.SDK_INT: 30
Build.MANUFACTURER: samsung
LeakCanary version: 2.12
App process name: com.hjq.window.demo
Class count: 33378
Instance count: 152400
Primitive array count: 132675
Object array count: 31706
Thread count: 16
Heap total bytes: 30134282
Bitmap count: 2
Bitmap total bytes: 218862
Large bitmap count: 0
Large bitmap total bytes: 0
Stats: LruCache[maxSize=3000,hits=40763,misses=114157,hitRate=26%]
RandomAccess[bytes=5272773,reads=114157,travel=61171251196,range=34940109,size=44410626]
Analysis duration: 4512 ms

Screen_Recording_20240601-192419_EasyWindow.mp4

框架文档是否提及了该问题【必答】

否

是否已经查阅框架文档但还未能解决的【必答】

否

issue 列表中是否有人曾提过类似的问题【必答】

否

是否已经搜索过了 issue 列表但还未能解决的【必答】

是

[Android轮子哥]

小伙子，你确定 issue 列表没有人提过这个问题？