Too many Binders sent to SYSTEM and kill my app

[Jun19]

MAX SDK Version

11.11.3

Device/Platform Info

Android13、PIXEL4

Current Behavior

After initializing the SDK for a few seconds, the application was directly killed I think it's a problem with the immobi adapter because this behavior won't occur when I comment it out

2023-11-14 11:20:56.141 1866-3858 BpBinder system_server E Too many binder proxy objects sent to uid 1000 from uid 10655 (6000 proxies held) 2023-11-14 11:20:56.141 1866-1993 ActivityManager system_server E Uid 10655 sent too many Binders to uid 1000 2023-11-14 11:20:56.142 1866-1993 ActivityManager system_server I Killing 18885:com.sasa.asasa/u0a655 (adj 0): Too many Binders sent to SYSTEM

use adb shell dumpsys meminfo packagename can see

Expected Behavior

No response

How to Reproduce

After initializing the SDK for a few seconds

dependics :+--- com.applovin:applovin-sdk:+ -> 11.11.3 | +--- com.google.android.gms:play-services-ads-identifier:17.1.0 -> 18.0.1 () | --- com.google.android.gms:play-services-appset:16.0.0 -> 16.0.2 | +--- com.google.android.gms:play-services-base:18.0.1 | | +--- androidx.collection:collection:1.0.0 -> 1.1.0 () | | +--- androidx.core:core:1.2.0 -> 1.9.0 () | | +--- androidx.fragment:fragment:1.0.0 -> 1.1.0 () | | +--- com.google.android.gms:play-services-basement:18.0.0 -> 18.1.0 () | | --- com.google.android.gms:play-services-tasks:18.0.1 -> 18.0.2 | | --- com.google.android.gms:play-services-basement:18.1.0 () | +--- com.google.android.gms:play-services-basement:18.0.0 -> 18.1.0 () | --- com.google.android.gms:play-services-tasks:18.0.1 -> 18.0.2 () +--- com.applovin.mediation:inmobi-adapter:+ -> 10.6.2.0 | --- com.inmobi.monetization:inmobi-ads-kotlin:10.6.2 | +--- com.inmobi.omsdk:inmobi-omsdk:1.3.17.1 | +--- com.google.android.gms:play-services-ads-identifier:18.0.1 () | +--- androidx.recyclerview:recyclerview:1.2.1 () | +--- com.squareup.picasso:picasso:2.8 | | +--- com.squareup.okhttp3:okhttp:3.10.0 -> 4.9.3 () | | +--- androidx.annotation:annotation:1.0.0 -> 1.2.0 | | --- androidx.exifinterface:exifinterface:1.0.0 | | --- androidx.annotation:annotation:1.0.0 -> 1.2.0 | +--- androidx.browser:browser:1.4.0 | | +--- androidx.collection:collection:1.1.0 () | | +--- androidx.concurrent:concurrent-futures:1.0.0 -> 1.1.0 () | | +--- androidx.interpolator:interpolator:1.0.0 () | | +--- androidx.core:core:1.1.0 -> 1.9.0 () | | +--- androidx.annotation:annotation:1.1.0 -> 1.2.0 | | --- com.google.guava:listenablefuture:1.0 | +--- org.jetbrains.kotlin:kotlin-reflect:1.5.30 | | --- org.jetbrains.kotlin:kotlin-stdlib:1.5.30 -> 1.8.10 () | +--- androidx.core:core-ktx:1.5.0 -> 1.9.0 () | +--- com.google.android.gms:play-services-appset:16.0.2 () | --- com.google.android.gms:play-services-tasks:18.0.2 (*)

Additional Info

No response

[Jun19]

I hope someone can track this issue as soon as possible, at least to determine whether it is a max inbobi adapter issue or an inbobi original SDK issue

[Jun19]

Immobi fixed