We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The library has memory leak. I found it with leak canary.
┬─── │ GC Root: Local variable in native code │ ├─ android.os.HandlerThread instance │ Leaking: NO (PathClassLoader↓ is not leaking) │ Thread name: 'LeakCanary-Heap-Dump' │ ↓ Thread.contextClassLoader ├─ dalvik.system.PathClassLoader instance │ Leaking: NO (Takt↓ is not leaking and A ClassLoader is never leaking) │ ↓ ClassLoader.runtimeInternalObjects ├─ java.lang.Object[] array │ Leaking: NO (Takt↓ is not leaking) │ ↓ Object[].[3001] ├─ jp.wasabeef.takt.Takt class │ Leaking: NO (a class is never leaking) │ ↓ static Takt.program │ ~~~~~~~ ├─ jp.wasabeef.takt.Takt$Program instance │ Leaking: UNKNOWN │ Retaining 5.4 kB in 109 objects │ app instance of com.zbs.android.App │ ↓ Takt$Program.stageView │ ~~~~~~~~~ ╰→ android.widget.RelativeLayout instance Leaking: YES (ObjectWatcher was watching this because android.widget. RelativeLayout received View#onDetachedFromWindow() callback) Retaining 1.7 kB in 37 objects key = f8ab425e-a992-47fd-8b92-4b209925b054 watchDurationMillis = 5262 retainedDurationMillis = 224 key = bfb77bf7-2c19-430a-8b3a-049ced24122f key = 2383ccf8-6ff7-4f82-82ab-16aba79fc564 watchDurationMillis = 5263 key = 125a0c09-786f-4d1a-8414-81d3d81a695b retainedDurationMillis = 225 View not part of a window view hierarchy View.mAttachInfo is null (view detached) View.mWindowAttachCount = 4 mContext instance of com.zbs.android.App
METADATA
Build.VERSION.SDK_INT: 29 Build.MANUFACTURER: Xiaomi LeakCanary version: 2.6 App process name: com.zbs.android Stats: LruCache[maxSize=3000,hits=5711,misses=65587,hitRate=8%] RandomAccess[bytes=3694801,reads=65587,travel=27211795232,range=22255045,size=26 931632] Heap dump reason: 4 retained objects, app is not visible Analysis duration: 6717 ms
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The library has memory leak. I found it with leak canary.
┬───
│ GC Root: Local variable in native code
│
├─ android.os.HandlerThread instance
│ Leaking: NO (PathClassLoader↓ is not leaking)
│ Thread name: 'LeakCanary-Heap-Dump'
│ ↓ Thread.contextClassLoader
├─ dalvik.system.PathClassLoader instance
│ Leaking: NO (Takt↓ is not leaking and A ClassLoader is never leaking)
│ ↓ ClassLoader.runtimeInternalObjects
├─ java.lang.Object[] array
│ Leaking: NO (Takt↓ is not leaking)
│ ↓ Object[].[3001]
├─ jp.wasabeef.takt.Takt class
│ Leaking: NO (a class is never leaking)
│ ↓ static Takt.program
│ ~~~~~~~
├─ jp.wasabeef.takt.Takt$Program instance
│ Leaking: UNKNOWN
│ Retaining 5.4 kB in 109 objects
│ app instance of com.zbs.android.App
│ ↓ Takt$Program.stageView
│ ~~~~~~~~~
╰→ android.widget.RelativeLayout instance
Leaking: YES (ObjectWatcher was watching this because android.widget.
RelativeLayout received View#onDetachedFromWindow() callback)
Retaining 1.7 kB in 37 objects
key = f8ab425e-a992-47fd-8b92-4b209925b054
watchDurationMillis = 5262
retainedDurationMillis = 224
key = bfb77bf7-2c19-430a-8b3a-049ced24122f
key = 2383ccf8-6ff7-4f82-82ab-16aba79fc564
watchDurationMillis = 5263
key = 125a0c09-786f-4d1a-8414-81d3d81a695b
retainedDurationMillis = 225
View not part of a window view hierarchy
View.mAttachInfo is null (view detached)
View.mWindowAttachCount = 4
mContext instance of com.zbs.android.App
METADATA
Build.VERSION.SDK_INT: 29
Build.MANUFACTURER: Xiaomi
LeakCanary version: 2.6
App process name: com.zbs.android
Stats: LruCache[maxSize=3000,hits=5711,misses=65587,hitRate=8%]
RandomAccess[bytes=3694801,reads=65587,travel=27211795232,range=22255045,size=26
931632]
Heap dump reason: 4 retained objects, app is not visible
Analysis duration: 6717 ms
The text was updated successfully, but these errors were encountered: