IntercomMessengerActivity memory leak

Hi, everyone!
We have some troubles with Intercom android sdk version 6.1. We are using LeakCanary and we’ve got this trace from it:

Memory leaks 1
┬───
│ GC Root: Input or output parameters in native code
│
├─ android.os.MessageQueue instance
│    Leaking: NO (MessageQueue#mQuitting is false)
│    ↓ MessageQueue.mMessages
│                   ~~~~~~~~~
├─ android.os.Message instance
│    Leaking: UNKNOWN
│    ↓ Message.next
│              ~~~~
├─ android.os.Message instance
│    Leaking: UNKNOWN
│    ↓ Message.callback
│              ~~~~~~~~
├─ io.intercom.android.sdk.views.holder.PartViewHolder$3 instance
│    Leaking: UNKNOWN
│    Anonymous class implementing java.lang.Runnable
│    ↓ PartViewHolder$3.this$0
│                       ~~~~~~
├─ io.intercom.android.sdk.views.holder.PartViewHolder instance
│    Leaking: UNKNOWN
│    ↓ PartViewHolder.attribution
│                     ~~~~~~~~~~~
├─ androidx.appcompat.widget.AppCompatTextView instance
│    Leaking: YES (View.mContext references a destroyed activity)
│    mContext instance of io.intercom.android.sdk.activities.IntercomMessengerActivity with mDestroyed = true
│    View#mParent is set
│    View#mAttachInfo is null (view detached)
│    View.mID = R.id.attribution
│    View.mWindowAttachCount = 1
│    ↓ AppCompatTextView.mContext
╰→ io.intercom.android.sdk.activities.IntercomMessengerActivity instance
      Leaking: YES (ObjectWatcher was watching this because io.intercom.android.sdk.activities.IntercomMessengerActivity received Activity#onDestroy() callback and Activity#mDestroyed is true)
      key = 7d9ffe48-4cb9-47c0-9f23-c4f887f8adcf
      watchDurationMillis = 18329
      retainedDurationMillis = 13329

METADATA

Build.VERSION.SDK_INT: 29
Build.MANUFACTURER: samsung
LeakCanary version: 2.3
Analysis duration: 10301 ms

and this

Memory leaks 2

┬───
│ GC Root: System class

├─ android.app.ActivityThread class
│ Leaking: NO (IntercomMessengerActivity↓ is not leaking and a class is never leaking)
│ ↓ static ActivityThread.sCurrentActivityThread
├─ android.app.ActivityThread instance
│ Leaking: NO (IntercomMessengerActivity↓ is not leaking)
│ ↓ ActivityThread.mTopActivityClient
├─ android.app.ActivityThread$ActivityClientRecord instance
│ Leaking: NO (IntercomMessengerActivity↓ is not leaking)
│ ↓ ActivityThread$ActivityClientRecord.activity
├─ io.intercom.android.sdk.activities.IntercomMessengerActivity instance
│ Leaking: NO (HomeFragment↓ is not leaking and Activity#mDestroyed is false)
│ ↓ IntercomMessengerActivity.homeFragment
├─ io.intercom.android.sdk.homescreen.HomeFragment instance
│ Leaking: NO (Fragment#mFragmentManager is not null)
│ Fragment.mTag=io.intercom.android.sdk.homescreen.HomeFragment
│ ↓ HomeFragment.rootView
│ ~~~~~~~~
╰→ androidx.constraintlayout.widget.ConstraintLayout instance
Leaking: YES (ObjectWatcher was watching this because io.intercom.android.sdk.homescreen.HomeFragment received Fragment#onDestroyView() callback (references to its views should be cleared to prevent leaks))
key = 84ac93a7-a0a0-4f6d-8db6-deefdd7451ba
watchDurationMillis = 3704
retainedDurationMillis = -1
mContext instance of io.intercom.android.sdk.activities.IntercomMessengerActivity with mDestroyed = false
View#mParent is null
View#mAttachInfo is null (view detached)
View.mID = R.id.home_coordinator_layout
View.mWindowAttachCount = 1

METADATA

Build.VERSION.SDK_INT: 29
Build.MANUFACTURER: samsung
LeakCanary version: 2.3
Analysis duration: 10120 ms

Do you know something about this? Could you help us to solve this problem?

Hello there! :wave:

Kayvan from Intercom customer support here. Could you please send us a message regarding this issue through the Messenger on your workspace? Our team would be happy to have a closer look into this. When you write in please also include the link to this post so that our Support Engineers can review the information you have provided here. We look forward to hearing from you! :slightly_smiling_face: