Android OOM Crash SDK v20.2.0

[Katie Lewis]

Hello,

We are seeing an increasing number of crashes from the Google SDK related to this thread: https://groups.google.com/g/google-admob-ads-sdk/c/pujkgoldM2s

We're on SDK v20.2.0 and I've shared the stack trace below. In terms of devices, it's predominantly lower end devices with around half the crashes are happening on Motorola devices.

Given this has been reported by several other pubs, is there already a case open for it and if so, do you know what stage this is at in terms of a fix?

Thanks

Katie

--

java.lang.OutOfMemoryError: pthread_create (1040KB stack) failed: Try again   at java.lang.Thread.nativeCreate(Native Method)   at java.lang.Thread.start(Thread.java:883)   at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:975)   at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1393)   at com.google.android.gms.tasks.Tasks.call(SourceFile:5)   at com.google.android.gms.internal.ads.zzfbb.zzb(SourceFile:2)   at com.google.android.gms.ads.internal.zzi.<init>(SourceFile:9)   at com.google.android.gms.internal.ads.zzckc.zze(SourceFile:1)   at com.google.android.gms.internal.ads.zzckg.zzb(SourceFile:1)   at com.google.android.gms.internal.ads.zzgdp.zzb(SourceFile:1)   at com.google.android.gms.internal.ads.zzdlv.zzb(SourceFile:1)   at com.google.android.gms.internal.ads.zzgdp.zzb(SourceFile:1)   at com.google.android.gms.internal.ads.zzcko.zzb(SourceFile:1)   at com.google.android.gms.internal.ads.zzgdp.zzb(SourceFile:1)   at com.google.android.gms.internal.ads.zzcmk.zzy(SourceFile:1)   at com.google.android.gms.internal.ads.zzegb.zza(SourceFile:24)   at com.google.android.gms.internal.ads.zzefp.zzb(SourceFile:3)   at com.google.android.gms.internal.ads.zzeek.zze(SourceFile:1)   at com.google.android.gms.ads.AdLoader.zza(SourceFile:1)   at com.google.android.gms.ads.AdLoader.loadAd(SourceFile:1)   at com.mopub.nativeads.GooglePlayServicesNative$GooglePlayServicesNativeAd.loadAd(SourceFile:45)   at com.mopub.nativeads.GooglePlayServicesNative.loadNativeAd(SourceFile:14)   at com.mopub.nativeads.CustomEventNativeAdapter.loadNativeAd(SourceFile:15)   at com.mopub.nativeads.MoPubNative.onAdLoad(SourceFile:7)   at com.mopub.nativeads.MoPubNative.access$000(SourceFile:1)   at com.mopub.nativeads.MoPubNative$2.onResponse(SourceFile:2)   at com.mopub.nativeads.MoPubNative$2.onResponse(SourceFile:1)   at com.mopub.network.AdLoader.deliverResponse(SourceFile:7)   at com.mopub.network.AdLoader.access$400(SourceFile:1)   at com.mopub.network.AdLoader$4.run(SourceFile:1)   at android.os.Handler.handleCallback(Handler.java:883)   at android.os.Handler.dispatchMessage(Handler.java:100)   at android.os.Looper.loop(Looper.java:214)   at android.app.ActivityThread.main(ActivityThread.java:7386)   at java.lang.reflect.Method.invoke(Native Method)   at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)   at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:980)

[Mobile Ads SDK Forum Advisor]

Hello Katie,

Thank you for reaching out to us.

For us to further investigate this, could you please provide the following details via Reply privately to author option or send it directly to mobileads...@gmail.com? Kindly inform us on this thread if you sent it directly to the email provided.

• Sample app
• Steps to replicate
• Device and versions used

Regards,

Princess Pamela Pineda Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2R7G13:ref

[itzno...@gmail.com]

Here's some more info. which shows that the crash seems to be originating from custom ExoPlayer usage in the library.

SDK Version: 20.5.0

Fatal Exception: java.lang.OutOfMemoryError: pthread_create (1040KB stack) failed: Try again
       at java.lang.Thread.nativeCreate(Thread.java)
       at java.lang.Thread.start(Thread.java:887)
       at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:977)
       at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1384)
       at java.util.concurrent.Executors$DelegatedExecutorService.execute(Executors.java:630)
       at com.google.android.gms.ads.exoplayer3.upstream.n.c(n.java)
       at com.google.android.gms.ads.exoplayer3.upstream.n.b(n.java:3)
       at com.google.android.gms.ads.exoplayer3.source.i.r(i.java:5)
       at com.google.android.gms.ads.exoplayer3.source.i.n(i.java)
       at com.google.android.gms.ads.exoplayer3.n.handleMessage(n.java:18)
       at android.os.Handler.dispatchMessage(Handler.java:102)
       at android.os.Looper.loop(Looper.java:223)
       at android.os.HandlerThread.run(HandlerThread.java:67)

[Mobile Ads SDK Forum Advisor]

Hello,

Thank you for reaching out to us.

It seems that you already have an existing forum thread created for this issue. Let's utilize that thread instead for better tracking of the issue.

Regards,

Mark Kevin Albios Mobile Ads SDK Team

ref:_00D1U1174p._5004Q2R7G13:ref

[mastef ‎]

Hi,

It seems the linked thread is not about the pthread_create OOM issue.

Possibly related thread : https://groups.google.com/g/google-admob-ads-sdk/c/pujkgoldM2s/m/6kPzzIx7BAAJ