still got crashes with Admob :/

276 views
Skip to first unread message

Mohamed Ouriachi

unread,
Aug 6, 2019, 4:39:24 AM8/6/19
to Google Mobile Ads SDK Developers
Hi there!


I ypdate my admob SDK to the latest 18.1.1 but i still got crashes :

  java.lang.OutOfMemoryError:
at java.lang.VMThread.create (Native Method)
at java.lang.Thread.start (Thread.java:1029)
at java.util.concurrent.ThreadPoolExecutor.addWorker (ThreadPoolExecutor.java:920)
at java.util.concurrent.ThreadPoolExecutor.execute (ThreadPoolExecutor.java:1338)
at com.google.android.gms.internal.ads.zzawy.execute
at com.google.android.gms.internal.ads.zzbgo.zza
at com.google.android.gms.internal.ads.zzbbf.zzh
at com.google.android.gms.internal.ads.zzbby.zzh
at com.google.android.gms.internal.ads.zzbbz.zzfl
at com.google.android.gms.internal.ads.zzbcb.run
at android.os.Handler.handleCallback (Handler.java:733)
at android.os.Handler.dispatchMessage (Handler.java:95)
at com.google.android.gms.internal.ads.zzczj.zzb
at com.google.android.gms.internal.ads.zzatp.zzb
at com.google.android.gms.internal.ads.zzczj.dispatchMessage
at android.os.Looper.loop (Looper.java:136)
at android.app.ActivityThread.main (ActivityThread.java:5086)
at java.lang.reflect.Method.invokeNative (Native Method)
at java.lang.reflect.Method.invoke (Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:785)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:601)
at dalvik.system.NativeStart.main (Native Method)

And this one :

id: 0, tid: 0 >>> com.kama_studio.fr.quatreimagesuneidee <<< backtrace:
#00 pc 0000000000000002 <unknown>
#01 pc 000000000018d41b /system/lib/libwebviewchromium.so
#02 pc 0000000000194521 /system/lib/libwebviewchromium.so
#03 pc 000000000001dd8c /system/lib/libdvm.so (dvmPlatformInvoke+112)
#04 pc 000000000004e253 /system/lib/libdvm.so (dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)+398)
#05 pc 00000000000271a0 /system/lib/libdvm.so
#06 pc 000000000002e150 /system/lib/libdvm.so (dvmMterpStd(Thread*)+76)
#07 pc 000000000002b7fc /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+184)
#08 pc 0000000000060b25 /system/lib/libdvm.so (dvmInvokeMethod(Object*, Method const*, ArrayObject*, ArrayObject*, ClassObject*, bool)+392)
#09 pc 0000000000068ab7 /system/lib/libdvm.so
#10 pc 00000000000271a0 /system/lib/libdvm.so
#11 pc 000000000002e150 /system/lib/libdvm.so (dvmMterpStd(Thread*)+76)
#12 pc 000000000002b7fc /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+184)
#13 pc 0000000000060843 /system/lib/libdvm.so (dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)+338)
#14 pc 0000000000049e3b /system/lib/libdvm.so
#15 pc 000000000004edbf /system/lib/libandroid_runtime.so
#16 pc 00000000000506b7 /system/lib/libandroid_runtime.so (android::AndroidRuntime::start(char const*, char const*, bool)+358)
#17 pc 0000000000001063 /system/bin/app_process
#18 pc 000000000000e463 /system/lib/libc.so (__libc_init+50)
#19 pc 0000000000000d80 /system/bin/app_process



Did i had to doi something more than update this SDk to get rid of those crashes ?



Thanks.

Mobile Ads SDK Forum Advisor Prod

unread,
Aug 6, 2019, 4:56:17 AM8/6/19
to fier...@gmail.com, google-adm...@googlegroups.com
Hi Mohamed,

Thank you for reporting this.

As per checking, the fix on this issue is in place but wasn't release yet and, I'm afraid that we cannot provide a definite timeline on when the fix will be release. 
Please keep an eye on our blog or our release notes regarding this.

Regards,
Teejay Pimentel
Mobile Ads SDK Team

ref:_00D1U1174p._5001UEI0qq:ref

Mohamed Ouriachi

unread,
Aug 6, 2019, 4:59:08 AM8/6/19
to Google Mobile Ads SDK Developers
Thanks for your quick reply;

I didn't use yet the 


yet.
can this cause the crashes or more crashes or not ?

Mobile Ads SDK Forum Advisor Prod

unread,
Aug 6, 2019, 6:21:53 AM8/6/19
to fier...@gmail.com, google-adm...@googlegroups.com
Hi Mohamed,

That is the step which is required as of Google Mobile Ads SDK version 17.0.0 and above. Failure to this <meta-data> tag results in a crash with the message: "The Google Mobile Ads SDK was initialized incorrectly. 

I'll update this thread as soon as the fix has been release.

Mohamed Ouriachi

unread,
Aug 6, 2019, 7:25:58 AM8/6/19
to Google Mobile Ads SDK Developers
Yes sorry i made a mistake i use  MobileAds.initialize(Context, OnInitializationCompleteListener) 
 sorry again :)
Message has been deleted

Mobile Ads SDK Forum Advisor Prod

unread,
Sep 9, 2019, 11:11:14 PM9/9/19
to brun...@gmail.com, google-adm...@googlegroups.com
Hi there,


Thank you for reporting this.

Is the issue locally reproducible on your end? If so, please provide a project (or at least a test project) along with the Charles log (see instruction here) capturing the behavior.
Kindly use the "Reply Privately to Author" option to share the details privately.
Message has been deleted

Mobile Ads SDK Forum Advisor Prod

unread,
Oct 11, 2019, 2:52:45 AM10/11/19
to brun...@gmail.com, google-adm...@googlegroups.com
Hi there,

I'm afraid that we're left with not much of an option here as we'll need a detailed debug information from a device where it's observed in order to actually make any progress in diagnosing this. The only way for us to investigate further is by capturing the Charles log while reproducing the issue, as this will enable us to replicate the behavior in our test app environment (by trafficking the creative in the test network).

With that said, please provide us the Charles log (see instruction here) so we could further investigate the issue.

Lisitso

unread,
Jun 8, 2020, 10:37:09 AM6/8/20
to Google Mobile Ads SDK Developers
Hi, I'm still getting these crashreports, only from Android 4.4 devices.
Any workaround to prevent app crash due to ads?

Best Regards


backtrace:
#00 pc 0000000000000002 <unknown>
#01 pc 000000000018d41b /system/lib/libwebviewchromium.so
#02 pc 0000000000194521 /system/lib/libwebviewchromium.so
#03 pc 000000000001dd8c /system/lib/libdvm.so (dvmPlatformInvoke+112)
#04 pc 000000000004e253 /system/lib/libdvm.so (dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)+398)
#05 pc 00000000000271a0 /system/lib/libdvm.so
#06 pc 000000000002e150 /system/lib/libdvm.so (dvmMterpStd(Thread*)+76)
#07 pc 000000000002b7fc /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+184)
#08 pc 0000000000060b25 /system/lib/libdvm.so (dvmInvokeMethod(Object*, Method const*, ArrayObject*, ArrayObject*, ClassObject*, bool)+392)
#09 pc 0000000000068ab7 /system/lib/libdvm.so
#10 pc 00000000000271a0 /system/lib/libdvm.so
#11 pc 000000000002e150 /system/lib/libdvm.so (dvmMterpStd(Thread*)+76)
#12 pc 000000000002b7fc /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+184)
#13 pc 0000000000060843 /system/lib/libdvm.so (dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)+338)
#14 pc 0000000000049e3b /system/lib/libdvm.so
#15 pc 000000000004ed5f /system/lib/libandroid_runtime.so
#16 pc 0000000000050657 /system/lib/libandroid_runtime.so (android::AndroidRuntime::start(char const*, char const*, bool)+358)

Mobile Ads SDK Forum Advisor Prod

unread,
Jun 8, 2020, 12:16:12 PM6/8/20
to andre...@gmail.com, google-adm...@googlegroups.com
Hi Lisitso,

Thank you for bringing this to our attention.

I just want to double check on one thing. When you say Android 4.4 we are talking about the version level. As such based on what you sent there was nothing in the backtrace that showed our SDK as being the cause of the crash. But at the same time if you are seeing crashes in such an older version there could be several reasons for that.

If you would want we can try to look over what you have. or if you send us more information we can try to look into it. But as I stated before. Crashes for such an old version with our SDK could cause crashes since the phones might not have enough memory to handle it.

Also I would ask what version of google play service are you using?

Regards,
William Pescherine

Mobile Ads SDK Team
 

ref:_00D1U1174p._5004Q20X4nw:ref

Lisitso

unread,
Jun 9, 2020, 3:42:39 AM6/9/20
to Google Mobile Ads SDK Developers
Hi William,
thank you for your prompt reply, really appreciated.
In my app I don't use webviews so I related the issue to the ads when I analyzed the backtrace.
I use different version of playservices according to the API/Feature used.
About ads, I use com.google.firebase:firebase-ads:18.0.0
I hope you can give me any suggestion to solve or mitigate the issue.

Regards,
Lisitso

Mobile Ads SDK Forum Advisor Prod

unread,
Jun 9, 2020, 6:22:48 AM6/9/20
to andre...@gmail.com, google-adm...@googlegroups.com
Hi Lisitso,

I work along with William. Thank you for getting back to us.

Were you able to reproduce the issue locally? If so, would it be possible for you to provide a sample project (or at least a test project) where the issue is reproducible? This will be a great help for us to investigate the issue further. Kindly send the requested details via Reply privately to author option.

Regards,
Teejay Pimentel

Lisitso

unread,
Jun 9, 2020, 6:54:14 AM6/9/20
to Google Mobile Ads SDK Developers
Hi Teejay,

thank you for your reply.
Unfortunately no, I was not able to reproduce the issue. May be it depends on the Ad (content) that the system served.
It's also actually impossible to debug these cases because the only information on the issue
is the raw backtrace coming from the Google developer dashboard (from Vitals, Crash)
As this is the top issue for my app, with increasing trend,
do you have any suggestment on what I could check?
In attachment some info I hope it could help.

Regards
Lisitso
AndroidDeveloperConsole001.png
backtrace001.txt

Mobile Ads SDK Forum Advisor Prod

unread,
Jun 9, 2020, 9:47:59 AM6/9/20
to andre...@gmail.com, google-adm...@googlegroups.com
Hi Lisitso,

Thank you for the addition information.

I have looked a little more into a few things that could be causing the issue.

There could be a possible conflict with your firebase google play and the Android 4.4 . I saw 2 things that coud be of assitance here.
  • First check out this link that shows how you might need extra dependencies. Look at release 18.0.0 and before that you will see a bunch of changes made to firebase.
  • Also I would suggest looking into this link , as it appears to show more about the possible changes made around that time. And for that service.
At the same time if you could pass along a simple sample app with the firebase implemented so we can test against it. This could help us to look further into this for you.

Regards,
William Pescherine
Reply all
Reply to author
Forward
0 new messages