Skip to content
New issue

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

TrinityRecord causes memory leak #120

Open
ZhengYiMin opened this issue Nov 27, 2020 · 0 comments
Open

TrinityRecord causes memory leak #120

ZhengYiMin opened this issue Nov 27, 2020 · 0 comments

Comments

@ZhengYiMin
Copy link

┬───
│ GC Root: Global variable in native code

├─ com.trinity.record.TrinityRecord instance
│ Leaking: UNKNOWN
│ Retaining 430106 bytes in 3720 objects
│ context instance of com.trinity.sample.RecordActivity with mDestroyed = true
│ mCameraCallback instance of com.trinity.sample.RecordActivity with mDestroyed = true
│ mOnRecordingListener instance of com.trinity.sample.RecordActivity with mDestroyed = true
│ mOnRenderListener instance of com.trinity.sample.RecordActivity with mDestroyed = true
│ ↓ TrinityRecord.context
│ ~~~~~~~
╰→ com.trinity.sample.RecordActivity instance
​ Leaking: YES (ObjectWatcher was watching this because com.trinity.sample.RecordActivity received
​ Activity#onDestroy() callback and Activity#mDestroyed is true)
​ Retaining 412217 bytes in 3266 objects
​ key = 1739672f-5265-4dbd-b9fc-f476cb0464cb
​ watchDurationMillis = 7768
​ retainedDurationMillis = 2767
​ mApplication instance of com.trinity.sample.TrinityApplication
​ mBase instance of android.app.ContextImpl, not wrapping known Android context
====================================
0 LIBRARY LEAKS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant