Skip to first unread message
Raymond Chan
May 7, 2020, 9:34:18 AM5/7/20
to Google Mobile Ads SDK Developers
Hi support,
We've encountered native crash related to latest AdMob SDK on Android 10. User encountered crash with our app: https://play.google.com/store/apps/details?id=com.ninegag.android.app
The crash will happen when user scroll through the list view, sometimes it will behave like the screen recording below:
The crash mostly come from certain types of devices including OnePlus, POCO and Samsung.
Here are screen recordings:
- https://youtu.be/YRUEVE7uGK8
(In app behaviour before crash, you will see items are stuttering, top
one is an ExoPlayer instance, the bottom one is a PublisherAdView)
- https://youtu.be/LqoTv4D7UYc (Chrome is not working on user's phone after our app is crashed, it's flickering) You may refer to the bugreport here, they are captured right after crash:
- https://drive.google.com/file/d/1NXrQlWT5DkWs2JsIev-4k-3haZtaX6B9/view?usp=sharing
- https://drive.google.com/file/d/1NXrQlWT5DkWs2JsIev-4k-3haZtaX6B9/view?usp=sharing
- https://drive.google.com/file/d/1bYIqwaJHq1GVaMQKHpC5MTjT_ixVYUo9/view?usp=drive_web (bugreport-OnePlus7_EEA-QKQ1.190716.003-2020-04-29-10-07-13.zip)
- https://drive.google.com/file/d/1A7t9O06QJ6FeKYdcmhbHhIAAUEeobjRR/view?usp=drive_web (bugreport-OnePlus7-QKQ1.190716.003-2020-04-20-09-37-48.zip)05-04 18:42:08.493 10294 20995 20995 I crash_dump64: performing dump of process 19569 (target tid = 19811)
05-04 18:42:08.505 10294 20995 20995 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-04 18:42:08.505 10294 20995 20995 F DEBUG : Build fingerprint: 'samsung/starqltesq/starqltesq:10/QP1A.190711.020/G960USQU7DTA5:user/release-keys'
05-04 18:42:08.505 10294 20995 20995 F DEBUG : Revision: '14'
05-04 18:42:08.505 10294 20995 20995 F DEBUG : ABI: 'arm64'
05-04 18:42:08.505 10294 20995 20995 F DEBUG : Timestamp: 2020-05-04 18:42:08+0800
05-04 18:42:08.505 10294 20995 20995 F DEBUG : pid: 19569, tid: 19811, name: Chrome_InProcGp >>> com.ninegag.android.app <<<
05-04 18:42:08.505 10294 20995 20995 F DEBUG : uid: 10294
05-04 18:42:08.505 10294 20995 20995 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x37b59f1447136fdd
05-04 18:42:08.505 10294 20995 20995 F DEBUG : x0 0000000000000001 x1 0000000000000020 x2 0000007e2d69b5f0 x3 0000007f05a00be8
05-04 18:42:08.506 10294 20995 20995 F DEBUG : x4 0000000000000008 x5 8000000000000000 x6 ff2f787371646f6e x7 7f7f7f7f7f7f7f7f
05-04 18:42:08.506 10294 20995 20995 F DEBUG : x8 0000007def95eb00 x9 0000000000000020 x10 37b59f1447136fcd x11 0000000000000000
05-04 18:42:08.506 10294 20995 20995 F DEBUG : x12 0000000000000000 x13 3d656572665f7061 x14 ffffffffffffffff x15 000000000000000a
05-04 18:42:08.506 10294 20995 20995 F DEBUG : x16 0000007f05921358 x17 0000007f9edc66f0 x18 0000007e4c37c000 x19 0000007e2d6243f0
05-04 18:42:08.506 10294 20995 20995 F DEBUG : x20 0000000000000001 x21 0000000000000020 x22 0000000000000020 x23 0000000000000000
05-04 18:42:08.506 10294 20995 20995 F DEBUG : x24 0000000000000000 x25 0000000000000000 x26 0000000000000000 x27 0000000000000001
05-04 18:42:08.506 10294 20995 20995 F DEBUG : x28 0000007e2d69b5f0 x29 0000007e4c91bde0
05-04 18:42:08.506 10294 20995 20995 F DEBUG : sp 0000007e4c91bdc0 lr 0000007ebd4f842c pc 0000007ebd4f8458
05-04 18:42:08.508 10294 20995 20995 F DEBUG :
05-04 18:42:08.508 10294 20995 20995 F DEBUG : backtrace:
05-04 18:42:08.508 10294 20995 20995 F DEBUG : #00 pc 0000000002937458 /data/app/com.google.android.webview-nOyLP2FqozztobnWHfVf3Q==/base.apk!libmonochrome.so (offset 0x1c3000) (BuildId: d3695837b0eaa100d32881715432e23fe3cadd03)
05-04 18:42:08.505 10294 20995 20995 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-04 18:42:08.505 10294 20995 20995 F DEBUG : Build fingerprint: 'samsung/starqltesq/starqltesq:10/QP1A.190711.020/G960USQU7DTA5:user/release-keys'
05-04 18:42:08.505 10294 20995 20995 F DEBUG : Revision: '14'
05-04 18:42:08.505 10294 20995 20995 F DEBUG : ABI: 'arm64'
05-04 18:42:08.505 10294 20995 20995 F DEBUG : Timestamp: 2020-05-04 18:42:08+0800
05-04 18:42:08.505 10294 20995 20995 F DEBUG : pid: 19569, tid: 19811, name: Chrome_InProcGp >>> com.ninegag.android.app <<<
05-04 18:42:08.505 10294 20995 20995 F DEBUG : uid: 10294
05-04 18:42:08.505 10294 20995 20995 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x37b59f1447136fdd
05-04 18:42:08.505 10294 20995 20995 F DEBUG : x0 0000000000000001 x1 0000000000000020 x2 0000007e2d69b5f0 x3 0000007f05a00be8
05-04 18:42:08.506 10294 20995 20995 F DEBUG : x4 0000000000000008 x5 8000000000000000 x6 ff2f787371646f6e x7 7f7f7f7f7f7f7f7f
05-04 18:42:08.506 10294 20995 20995 F DEBUG : x8 0000007def95eb00 x9 0000000000000020 x10 37b59f1447136fcd x11 0000000000000000
05-04 18:42:08.506 10294 20995 20995 F DEBUG : x12 0000000000000000 x13 3d656572665f7061 x14 ffffffffffffffff x15 000000000000000a
05-04 18:42:08.506 10294 20995 20995 F DEBUG : x16 0000007f05921358 x17 0000007f9edc66f0 x18 0000007e4c37c000 x19 0000007e2d6243f0
05-04 18:42:08.506 10294 20995 20995 F DEBUG : x20 0000000000000001 x21 0000000000000020 x22 0000000000000020 x23 0000000000000000
05-04 18:42:08.506 10294 20995 20995 F DEBUG : x24 0000000000000000 x25 0000000000000000 x26 0000000000000000 x27 0000000000000001
05-04 18:42:08.506 10294 20995 20995 F DEBUG : x28 0000007e2d69b5f0 x29 0000007e4c91bde0
05-04 18:42:08.506 10294 20995 20995 F DEBUG : sp 0000007e4c91bdc0 lr 0000007ebd4f842c pc 0000007ebd4f8458
05-04 18:42:08.508 10294 20995 20995 F DEBUG :
05-04 18:42:08.508 10294 20995 20995 F DEBUG : backtrace:
05-04 18:42:08.508 10294 20995 20995 F DEBUG : #00 pc 0000000002937458 /data/app/com.google.android.webview-nOyLP2FqozztobnWHfVf3Q==/base.apk!libmonochrome.so (offset 0x1c3000) (BuildId: d3695837b0eaa100d32881715432e23fe3cadd03)
Would you please take a look as we are frustrated about this bug. We don't have idea on which particular ads triggered this native crash and therefore we cannot ban those ads.
Mobile Ads SDK Forum Advisor Prod
May 7, 2020, 11:43:47 AM5/7/20
to google-adm...@googlegroups.com
Hi Raymond,
Thank you for bringing this crash to our attention and for the amount of details you were able to give us. I saw the before and after video and tried out your app and wasn't able to replicate the issue. I looked through the bug reports and one of them had an interesting find repeated twice:
04-29 10:06:01.860 10239 22644 22644 E SMAAdMobSmaatoBannerAdapter: Smaato banner ad failed to load. Error: [NO_AD_AVAILABLE]: No ad is currently available matching the requested parameters. Please try again later.
04-29 10:06:01.863 10239 22644 22899 W Ads : Could not load custom event implementation class: com.smaato.soma.MediationAdapter.AdMobMediationAdapter, assuming old implementation.
04-29 10:06:01.863 10239 22644 22899 W Ads : Could not instantiate mediation adapter: com.google.ads.mediation.customevent.CustomEventAdapter.
04-29 10:06:01.863 10239 22644 22899 W Ads : java.lang.NullPointerException: Attempt to invoke interface method 'java.lang.Object java.util.Map.get(java.lang.Object)' on a null object reference
04-29 10:06:01.863 10239 22644 22899 W Ads : at bnv.e(SourceFile:39)
04-29 10:06:01.863 10239 22644 22899 W Ads : at bnv.d(SourceFile:28)
04-29 10:06:01.863 10239 22644 22899 W Ads : at bnv.a(SourceFile:2)
04-29 10:06:01.863 10239 22644 22899 W Ads : at bny.a(SourceFile:11)
04-29 10:06:01.863 10239 22644 22899 W Ads : at ffk.onTransact(SourceFile:13)
04-29 10:06:01.863 10239 22644 22899 W Ads : at android.os.Binder.transact(Binder.java:925)
04-29 10:06:01.863 10239 22644 22899 W Ads : at ez.a(:com.google.android.gms.policy_ads_fdr_dynamite@21460000@21460000.297791526.297791526:2)
04-29 10:06:01.863 10239 22644 22899 W Ads : at com.google.android.gms.ads.internal.mediation.client.b.a(:com.google.android.gms.policy_ads_fdr_dynamite@21460000@21460000.297791526.297791526:1)
04-29 10:06:01.863 10239 22644 22899 W Ads : at com.google.android.gms.ads.nonagon.adapter.e.a(:com.google.android.gms.policy_ads_fdr_dynamite@21460000@21460000.297791526.297791526:10)
04-29 10:06:01.863 10239 22644 22899 W Ads : at com.google.android.gms.ads.nonagon.render.ax.a(:com.google.android.gms.policy_ads_fdr_dynamite@21460000@21460000.297791526.297791526:1)
04-29 10:06:01.863 10239 22644 22899 W Ads : at com.google.android.gms.ads.nonagon.render.dg.b(:com.google.android.gms.policy_ads_fdr_dynamite@21460000@21460000.297791526.297791526:2)
04-29 10:06:01.863 10239 22644 22899 W Ads : at com.google.android.gms.ads.nonagon.render.bz.a(:com.google.android.gms.policy_ads_fdr_dynamite@21460000@21460000.297791526.297791526:3)
04-29 10:06:01.863 10239 22644 22899 W Ads : at xt.a(:com.google.android.gms.policy_ads_fdr_dynamite@21460000@21460000.297791526.297791526:2)
04-29 10:06:01.863 10239 22644 22899 W Ads : at xv.run(:com.google.android.gms.policy_ads_fdr_dynamite@21460000@21460000.297791526.297791526:9)
04-29 10:06:01.863 10239 22644 22899 W Ads : at zu.run(:com.google.android.gms.policy_ads_fdr_dynamite@21460000@21460000.297791526.297791526:0)
04-29 10:06:01.863 10239 22644 22899 W Ads : at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
04-29 10:06:01.863 10239 22644 22899 W Ads : at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
04-29 10:06:01.863 10239 22644 22899 W Ads : at java.lang.Thread.run(Thread.java:919)
The other bug report didn't have this so it may not be causing the crash.
You also suggested it's a bad creative. To test this we would need a Charles log (SSL proxying must be enabled) of the crash. Debug tracing - https://developers.google.com/admob/android/network-tracing, could also be used but a Charles log is preferred.
To test this out on our end, via "Reply privately to author" could you send us the following?
Aryeh Baker
Mobile Ads SDK Team
ref:_00D1U1174p._5004Q1zKfQ4:ref
Thank you for bringing this crash to our attention and for the amount of details you were able to give us. I saw the before and after video and tried out your app and wasn't able to replicate the issue. I looked through the bug reports and one of them had an interesting find repeated twice:
04-29 10:06:01.860 10239 22644 22644 E SMAAdMobSmaatoBannerAdapter: Smaato banner ad failed to load. Error: [NO_AD_AVAILABLE]: No ad is currently available matching the requested parameters. Please try again later.
04-29 10:06:01.863 10239 22644 22899 W Ads : Could not load custom event implementation class: com.smaato.soma.MediationAdapter.AdMobMediationAdapter, assuming old implementation.
04-29 10:06:01.863 10239 22644 22899 W Ads : Could not instantiate mediation adapter: com.google.ads.mediation.customevent.CustomEventAdapter.
04-29 10:06:01.863 10239 22644 22899 W Ads : java.lang.NullPointerException: Attempt to invoke interface method 'java.lang.Object java.util.Map.get(java.lang.Object)' on a null object reference
04-29 10:06:01.863 10239 22644 22899 W Ads : at bnv.e(SourceFile:39)
04-29 10:06:01.863 10239 22644 22899 W Ads : at bnv.d(SourceFile:28)
04-29 10:06:01.863 10239 22644 22899 W Ads : at bnv.a(SourceFile:2)
04-29 10:06:01.863 10239 22644 22899 W Ads : at bny.a(SourceFile:11)
04-29 10:06:01.863 10239 22644 22899 W Ads : at ffk.onTransact(SourceFile:13)
04-29 10:06:01.863 10239 22644 22899 W Ads : at android.os.Binder.transact(Binder.java:925)
04-29 10:06:01.863 10239 22644 22899 W Ads : at ez.a(:com.google.android.gms.policy_ads_fdr_dynamite@21460000@21460000.297791526.297791526:2)
04-29 10:06:01.863 10239 22644 22899 W Ads : at com.google.android.gms.ads.internal.mediation.client.b.a(:com.google.android.gms.policy_ads_fdr_dynamite@21460000@21460000.297791526.297791526:1)
04-29 10:06:01.863 10239 22644 22899 W Ads : at com.google.android.gms.ads.nonagon.adapter.e.a(:com.google.android.gms.policy_ads_fdr_dynamite@21460000@21460000.297791526.297791526:10)
04-29 10:06:01.863 10239 22644 22899 W Ads : at com.google.android.gms.ads.nonagon.render.ax.a(:com.google.android.gms.policy_ads_fdr_dynamite@21460000@21460000.297791526.297791526:1)
04-29 10:06:01.863 10239 22644 22899 W Ads : at com.google.android.gms.ads.nonagon.render.dg.b(:com.google.android.gms.policy_ads_fdr_dynamite@21460000@21460000.297791526.297791526:2)
04-29 10:06:01.863 10239 22644 22899 W Ads : at com.google.android.gms.ads.nonagon.render.bz.a(:com.google.android.gms.policy_ads_fdr_dynamite@21460000@21460000.297791526.297791526:3)
04-29 10:06:01.863 10239 22644 22899 W Ads : at xt.a(:com.google.android.gms.policy_ads_fdr_dynamite@21460000@21460000.297791526.297791526:2)
04-29 10:06:01.863 10239 22644 22899 W Ads : at xv.run(:com.google.android.gms.policy_ads_fdr_dynamite@21460000@21460000.297791526.297791526:9)
04-29 10:06:01.863 10239 22644 22899 W Ads : at zu.run(:com.google.android.gms.policy_ads_fdr_dynamite@21460000@21460000.297791526.297791526:0)
04-29 10:06:01.863 10239 22644 22899 W Ads : at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
04-29 10:06:01.863 10239 22644 22899 W Ads : at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
04-29 10:06:01.863 10239 22644 22899 W Ads : at java.lang.Thread.run(Thread.java:919)
The other bug report didn't have this so it may not be causing the crash.
You also suggested it's a bad creative. To test this we would need a Charles log (SSL proxying must be enabled) of the crash. Debug tracing - https://developers.google.com/admob/android/network-tracing, could also be used but a Charles log is preferred.
To test this out on our end, via "Reply privately to author" could you send us the following?
- App Id and ad unit Id's
- Charles log of crash
- Logcat of crash
- Statistics from back end(Crashalytics) and error messages
- Gradle dependencies
- Steps to produce the crash if reliable
Aryeh Baker
Mobile Ads SDK Team
ref:_00D1U1174p._5004Q1zKfQ4:ref
Message has been deleted
Mobile Ads SDK Forum Advisor Prod
May 8, 2020, 10:06:15 AM5/8/20
to google-adm...@googlegroups.com
Hi Raymond,
Thank you for the ad Id's, Charles logs and extra clarification of when crash happened. Note that your scrubbed post is reposted below this response. I looked through the crash log during the time the crash occurred and didn't see the obvious symbol of a crash due to the Mobile Ads SDK which is not surprising. I also looked through the Charles log and saw no request - wether from AdMob or from Ad Manager. I also looked through your gradle files for the Mobile Ads SDK and didn't find it - you gave me the project gradle only. To check this issue out on our end could you send us via "Reply privately to author" the following?
Thank you for the ad Id's, Charles logs and extra clarification of when crash happened. Note that your scrubbed post is reposted below this response. I looked through the crash log during the time the crash occurred and didn't see the obvious symbol of a crash due to the Mobile Ads SDK which is not surprising. I also looked through the Charles log and saw no request - wether from AdMob or from Ad Manager. I also looked through your gradle files for the Mobile Ads SDK and didn't find it - you gave me the project gradle only. To check this issue out on our end could you send us via "Reply privately to author" the following?
- a sample project based on our sample apps with minimal code added necessary to reproduce your issue
- steps to take to reproduce the issue
Aryeh Baker
Mobile Ads SDK Team
Hi Aryeh,
Just captured Charles log and bug report right after the crash
Bug report
The crash occurred at around 16:17 - 16:19 HKT. You may need to check the tombstone log (tombstone_06), as this time I cannot find the native crash stacktrace above
build.gradle
App ID:
Ad Unit IDs:
ref:_00D1U1174p._5004Q1zKfQ4:ref
Reply all
Reply to author
Forward
0 new messages