Memory leak : Applovin.impl.mediation.debugger

[raghav2945]

Summary: This memory leak was found using leakcanary. Actually, we've noticed a rise in out-of-memory crashes since the MAX migration. And this is only one example.

Problem Statement: With integration design, we clearly share an application context during initialization, however it seems that your process binder stub implementation is holding onto the reference and not releasing it when the app is closed. As a result, it GC couldn't able to clear this instance.

appLovinAds.initialise( applicationContext,
listOf(
remoteVariablesProvider.appLovinBannerId,
remoteVariablesProvider.appLovinInterstitialId,
remoteVariablesProvider.appLovinMrecId
).filter { it.isNotBlank() },
preferencesRepository.appLovinConsentGranted
)

Workaround: I think a weak reference to the context in native is a likely workaround.

┬───
│ GC Root: Local variable in native code
│
├─ com.applovin.impl.sdk.network.e$a instance
│    Leaking: UNKNOWN
│    Retaining 336 B in 10 objects
│    Thread name: 'AL-Network-0'
│    ↓ e$a.b
│          ~
├─ com.applovin.impl.sdk.m instance
│    Leaking: UNKNOWN
│    Retaining 196.7 kB in 4316 objects
│    ↓ m.S
│        ~
├─ com.applovin.impl.mediation.debugger.a instance
│    Leaking: UNKNOWN
│    Retaining 57.3 kB in 1481 objects
│    k instance of com.audiomack.MainApplication
│    ↓ a.e
│        ~
├─ com.applovin.impl.mediation.debugger.ui.b.b instance
│    Leaking: UNKNOWN
│    Retaining 39.0 kB in 1055 objects
│    c instance of com.audiomack.ui.home.HomeActivity with mDestroyed = true
│    ↓ d.c
│        ~
╰→ com.audiomack.ui.home.HomeActivity instance
​     Leaking: YES (ObjectWatcher was watching this because com.audiomack.ui.
​     home.HomeActivity received Activity#onDestroy() callback and
​     Activity#mDestroyed is true)
​     Retaining 2.6 MB in 42013 objects
​     key = c0999466-18a6-45ed-8565-6332e58152ed
​     watchDurationMillis = 5335
​     retainedDurationMillis = 306
​     mApplication instance of com.audiomack.MainApplication
​     mBase instance of androidx.appcompat.view.ContextThemeWrapper

METADATA

Build.VERSION.SDK_INT: 29
Build.MANUFACTURER: Google
LeakCanary version: 2.7
App process name: com.audiomack
Count of retained yet cleared: 18 KeyedWeakReference instances
Stats: LruCache[maxSize=3000,hits=7317,misses=192272,hitRate=3%]
RandomAccess[bytes=8786648,reads=192272,travel=133040163296,range=39747896,size=
47178009]
Heap dump reason: 21 retained objects, app is not visible
Analysis duration: 9651 ms

[johnshazhu]

Have the same problem with config as follows:
========== MEDIATION DEBUGGER ==========
========== APP INFO ==========
Dev Build - true
Test Mode - disabled
Target SDK - 30
========== MAX ==========
SDK Version - 11.4.5
Plugin Version - None
Ad Review Version - Disabled
========== PRIVACY ==========
Age Restricted User - No value set
Has User Consent - No value set
"Do Not Sell" - No value set
========== NETWORKS ==========
---------- ADCOLONY_NETWORK ----------
Status - COMPLETE
SDK - UNAVAILABLE
Adapter - 4.6.5.1
---------- APPLOVIN_NETWORK ----------
Status - COMPLETE
SDK - 11.4.5
Adapter - 11.4.5
---------- INMOBI_NETWORK ----------
Status - COMPLETE
SDK - 10.0.3
Adapter - 10.0.3.1
---------- MINTEGRAL_BIDDING ----------
Status - COMPLETE
SDK - MAL_16.0.11
Adapter - 16.0.11.0
---------- TIKTOK_BIDDING ----------
Status - COMPLETE
SDK - 4.5.0.3
Adapter - 4.5.0.3.0
---------- SMAATO_NETWORK ----------
Status - COMPLETE
SDK - 21.6.7
Adapter - 21.6.7.2

[thomasmso]

Hi,

Could you add this code prior to initializing our SDK?

        val settings = new AppLovinSdkSettings( context );
        settings.setExtraParameter( "run_in_release_mode", "true" );

        val sdk = AppLovinSdk.getInstance( settings, context );
        sdk.setMediationProvider( "max" );
        sdk.initializeSdk( (AppLovinSdkConfiguration config) -> {
            ...
        } );

[johnshazhu]

Great! It works for me.

[thomasmso]

Glad to hear. When our SDK detects that it is being ran in debug mode (from your Android Studio) it runs the Mediation Debugger and its integration checks for you. The leak is from that.

[thomasmso]

Hey all - we pushed out v11.5.0 which fixes the aforementioned leak.