LeakCanary reports a leak about chucker HOT 12 CLOSED

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

from chucker.

It seems to be not Chucker issue: square/leakcanary#1594

from chucker.

Closing as an issue not related to the library.

from chucker.

Thanks for the report @niltsiar
I'm leaving this opened and free to pickup if someone wants to investigate more what's going on.

from chucker.

@niltsiar is this reproducible? I was unable to reproduce this on Android Q beta 7.
@cortinico my guess is activity was destroyed while viewpager was still in transaction. this is a bleak possibilty.

from chucker.

@adtyx it's reproducible every time using Android Q Beta 6, with my own projects and with Chucker sample. As far as I know there is no such beta 7, at least for Pixel devices.

I've made a test just leaving setContentView as the only thing the MainActivity does and also removing the ViewPager from the XML. The leak still appears.

from chucker.

@niltsiar is this reproducible? I was unable to reproduce this on Android Q beta 7.

@adtyx I saw it happening from time to time on a Pixel3, latest Android Q beta. I haven't really investigated on this but I'll be happy to assign this issue to a volunteer :)

from chucker.

I've tested it again with the new final version of Android 10. I've also updated my local copy of Chucker sample to use the latest LeakCanary-2.0-beta-3 and the issue is still happening.

from chucker.

On the last update of Android 10 on OnePlus 7 this leak is not being reported anymore. So there's a great chance it's been fixed. I had to uninstall the app and reinstall it though

from chucker.

I'm still seeing this issue.

Known leak pattern: instance field android.app.Activity$1#this$0
Description: Android Q added a new android.app.IRequestFinishCallback$Stub class. android.app.Activity creates an implementation of that interface as an anonymous subclass. That anonymous subclass has a reference to the activity. Another process is keeping the android.app.IRequestFinishCallback$Stub reference alive long after Activity.onDestroyed() has been called, causing the activity to leak.
338984 bytes retained
┬
├─ 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 = 274de02a-4a5e-4767-8367-3db4c6b397c1
​     watchDurationMillis = 5124
​     retainedDurationMillis = 120


METADATA

Build.VERSION.SDK_INT: 29
Build.MANUFACTURER: Google
LeakCanary version: 2.0
App process name: com.myapp
Analysis duration: 5785 ms

from chucker.

@aoben10 thanks for the LeakCanary report. From which version of Chucker is this related? Can I ask you to try using the latest SNAPSHOT from develop and confirm that is happening again?

from chucker.

Thanks for letting me know @vbuberen

from chucker.