After interstitial ad, app goes to ANR

[abdulkadirgun]

After watching interstitial ads, sometimes screen goes black and the application goes into ANR(11.4.4). What is the reason? Does anyone have this problem
thanks...

[thomasmso]

@abdulkadirgun - Could you share our SDK's verbose logs? We'd love to track down the exact ad causing this issue.

[abdulkadirgun]

173181909-7cf56456-fc9f-4bbb-96b2-59b724893c85.mp4

I have never experienced this problem. However, my users are constantly reporting that they are experiencing problems. I am sharing a video from my user with you. also only android 12s have this problem.
thanks...

[Adil-Sattar]

I am also getting memory leak when showing full scree ad => Interstitial on latest SDK

[abdulkadirgun]

this is memory leak trace from "leakCanary"

┬───
│ GC Root: Input or output parameters in native code
│
├─ android.os.MessageQueue instance
│ Leaking: NO (MessageQueue#mQuitting is false)
│ HandlerThread: "main"
│ ↓ MessageQueue[0]
│ ~~~
├─ android.os.Message instance
│ Leaking: UNKNOWN
│ Retaining 321 B in 11 objects
│ Message.what = 0
│ Message.when = 13031668 (9 ms after heap dump)
│ Message.obj = null
│ Message.callback = instance @350871336 of com.applovin.impl.sdk.aa$1
│ Message.target = instance @350871304 of android.os.Handler
│ ↓ Message.callback
│ ~~~~~~~~
├─ com.applovin.impl.sdk.aa$1 instance
│ Leaking: UNKNOWN
│ Retaining 232 B in 9 objects
│ Anonymous class implementing java.lang.Runnable
│ ↓ aa$1.b
│ ~
├─ com.applovin.impl.sdk.aa instance
│ Leaking: UNKNOWN
│ Retaining 192 B in 7 objects
│ ↓ aa.f
│ ~
├─ com.applovin.impl.sdk.aa$2 instance
│ Leaking: UNKNOWN
│ Retaining 16 B in 1 objects
│ Anonymous class implementing android.view.
│ ViewTreeObserver$OnPreDrawListener
│ ↓ aa$2.a
│ ~
├─ com.applovin.mediation.nativeAds.MaxNativeAdView instance
│ Leaking: YES (View.mContext references a destroyed activity)
│ Retaining 506.0 kB in 4993 objects
│ View not part of a window view hierarchy
│ View.mAttachInfo is null (view detached)
│ View.mWindowAttachCount = 1
│ mContext instance of com.viyatek.ultimatefacts.Activites.ArticleActivity
│ with mDestroyed = true
│ ↓ View.mParent
├─ android.widget.FrameLayout instance
│ Leaking: YES (MaxNativeAdView↑ is leaking and View.mContext references a
│ destroyed activity)
│ Retaining 421.7 kB in 3398 objects
│ View not part of a window view hierarchy
│ View.mAttachInfo is null (view detached)
│ View.mID = R.id.article_ad_fragment
│ View.mWindowAttachCount = 1
│ mContext instance of com.viyatek.ultimatefacts.Activites.ArticleActivity
│ with mDestroyed = true
│ ↓ View.mParent
├─ androidx.constraintlayout.widget.ConstraintLayout instance
│ Leaking: YES (FrameLayout↑ is leaking and View.mContext references a
│ destroyed activity)
│ Retaining 1.3 kB in 20 objects
│ View not part of a window view hierarchy
│ View.mAttachInfo is null (view detached)
│ View.mID = R.id.relativeLayout2
│ View.mWindowAttachCount = 1
│ mContext instance of com.viyatek.ultimatefacts.Activites.ArticleActivity
│ with mDestroyed = true
│ ↓ View.mParent
├─ androidx.core.widget.NestedScrollView instance
│ Leaking: YES (ConstraintLayout↑ is leaking and View.mContext references a
│ destroyed activity)
│ Retaining 2.0 kB in 35 objects
│ View not part of a window view hierarchy
│ View.mAttachInfo is null (view detached)
│ View.mID = R.id.article_view_pager_2
│ View.mWindowAttachCount = 1
│ mContext instance of com.viyatek.ultimatefacts.Activites.ArticleActivity
│ with mDestroyed = true
│ ↓ View.mParent
╰→ androidx.coordinatorlayout.widget.CoordinatorLayout instance
​ Leaking: YES (ObjectWatcher was watching this because com.viyatek.
​ ultimatefacts.Activites.ArticleFragment received Fragment#onDestroyView()
​ callback (references to its views should be cleared to prevent leaks) and
​ View.mContext references a destroyed activity)
​ Retaining 27.9 kB in 420 objects
​ key = 77df3266-2733-4b8b-9630-6d3feda983a7
​ watchDurationMillis = 5521
​ retainedDurationMillis = 520
​ View not part of a window view hierarchy
​ View.mAttachInfo is null (view detached)
​ View.mID = R.id.coordinator
​ View.mWindowAttachCount = 1
​ mContext instance of com.viyatek.ultimatefacts.Activites.ArticleActivity
​ with mDestroyed = true

[thomasmso]

We'll check this out, we've addressed some memory leaks in the next SDK release

[thomasmso]

Update on the thread - we've combed through various performance/memory issues in the SDK, and LeakCanary is no longer displaying any issues on our end.

[Adil-Sattar]

I am also getting memory leak when showing full scree ad => Interstitial on latest SDK

[thomasmso]

Can you describe the memory leak?

[Adil-Sattar]

One more thing kindly add the onclose override method in both interstitial and rewarded. its bad thing we start an activity with ad . activity must be start when ad close same like admob

…

On Tue, Aug 16, 2022, 10:07 PM Thomas So ***@***.***> wrote: We'll check this out, we've addressed some memory leaks in the next SDK release — Reply to this email directly, view it on GitHub <#354 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMRWPYCY33JRA6LF55ELMWDVZPDFZANCNFSM5574Y6FQ> . You are receiving this because you commented.Message ID: <AppLovin/AppLovin-MAX-SDK-Android/repo-discussions/354/comments/3408377@ github.com>

[Lzzzzzyy]

After I upgraded to 11.4.4, I also encountered the situation in the video. When I use Max test ad, it will not appear. Only real advertisements will appear. According to statistics, the devices that appear in this situation are mainly Samsung models. OS Android 12+，Is this problem fixed now？

[thomasmso]

@Lzzzzzyy - What version of our SDK did you update from?

[Lzzzzzyy]

11.4.3 to 11.4.4

[abdulkadirgun]

Hi, Is there any solution?

[abdulkadirgun]

Hi, Is there any solution?

[thomasmso]

We pushed v11.5.2 - is the issue still there?

[LegendAF]

Saw this today on a Samsung Galaxy S22

SDK v11.6.0

[selfnat]

The latest version of the screen becomes black still exists ah, there are many users feedback this problem