search

TheLastProject / RaiseToAnswer

Simply hold your phone to your ear to answer an incoming call
https://play.google.com/store/apps/details?id=me.hackerchick.raisetoanswer
MIT License
74 stars 13 forks source link

Memory leak #1

Closed TheLastProject closed 4 years ago

TheLastProject commented 4 years ago 
┬───
│ GC Root: System class
│
├─ android.app.ActivityThread class
│    Leaking: NO (a class is never leaking)
│    ↓ static ActivityThread.sCurrentActivityThread
│                            ~~~~~~~~~~~~~~~~~~~~~~
├─ android.app.ActivityThread instance
│    Leaking: UNKNOWN
│    ↓ ActivityThread.mServices
│                     ~~~~~~~~~
├─ android.util.ArrayMap instance
│    Leaking: UNKNOWN
│    ↓ ArrayMap.mArray
│               ~~~~~~
├─ java.lang.Object[] array
│    Leaking: UNKNOWN
│    ↓ Object[].[1]
│               ~~~
├─ me.hackerchick.raisetoanswer.RaiseToAnswerSensorEventListener instance
│    Leaking: UNKNOWN
│    RaiseToAnswerSensorEventListener does not wrap an activity context
│    ↓ RaiseToAnswerSensorEventListener.mContext
│                                       ~~~~~~~~
╰→ me.hackerchick.raisetoanswer.MainActivity instance
      Leaking: YES (ObjectWatcher was watching this because me.hackerchick.raisetoanswer.MainActivity received Activity#onDestroy() callback and Activity#mDestroyed is true)
      key = 515d0af7-a68e-45b9-8a8e-590e5bf740be
      watchDurationMillis = 5205
      retainedDurationMillis = 199

METADATA

Build.VERSION.SDK_INT: 28
Build.MANUFACTURER: Fairphone
LeakCanary version: 2.3
App process name: me.hackerchick.raisetoanswer
Analysis duration: 10116 ms
TheLastProject commented 4 years ago

Lots of refactoring, this is probably no longer relevant

MichaelJokAr commented 3 years ago

how do you solve this