LeakCanary reports a leak

Describe the bug LeakCanary reports a leak of MainActivity. I’ve been able to reproduce it in my own application and in the sample app. It doesn’t matter if there are captured network requests or not.

To Reproduce Steps to reproduce the behavior using the sample app:

1. Go to ‘LAUNCH CHUCKER DIRECTLY’
2. Click on ‘Back Button’
3. See error either in logcat or in LeakCanary UI

Screenshots LeakCanary result in logcat:

┬
├─ android.app.Activity$1
│    Leaking: UNKNOWN
│    Anonymous subclass of android.app.IRequestFinishCallback$Stub
│    GC Root: Global variable in native code
│    ↓ Activity$1.this$0
│                 ~~~~~~
╰→ com.chuckerteam.chucker.api.internal.ui.MainActivity
​     Leaking: YES (Activity#mDestroyed is true and ObjectWatcher was watching this)
​     key = 3d3901ea-a7b9-47fa-ba5a-566d1ede5924
​     watchDurationMillis = 5185
​     retainedDurationMillis = 178
, retainedHeapByteSize=165749)], libraryLeaks=[])

Smartphone

• Device: Pixel 3XL
• OS: Android Q Beta6
• Lib version: 3.0.1 and develop branch

Additional context I haven’t being able to reproduce it in other android versions. I suppose this is happening due to Android Q but I don’t know if it’s a false positive from LeakCanary or not. I’ve attached the memory dump from LeakCanary

2019-08-23_10-25-44_445.hprof.zip

[mrenouf]

It is a framework issue: https://issuetracker.google.com/issues/139738913

[vbuberen]

It seems to be not Chucker issue: https://github.com/square/leakcanary/issues/1594