signal 11 (SIGSEGV), code 1 (SEGV_MAPERR) in base.apk on Android 7.0+

[邱至民]

I have a banner ad in my app and it's crashing 400 times a day.

This problem has been existed almost a year.

High season of advertising, high error rate of this problem.

backtrace:

#00 pc 000000000249c658 /data/app/com.android.chrome-1/base.apk

#01 pc 000000000249c604 /data/app/com.android.chrome-1/base.apk

backtrace:

#00 pc 00007fa1207a2000 <unknown>

#01 pc 0000000000007fa4 /system/vendor/lib64/libgsl.so (gsl_syncobj_wait+88)

#02 pc 000000000019a770 /system/vendor/lib64/egl/libGLESv2_adreno.so (_ZN12EglFenceSync10ClientWaitEim+144)

#03 pc 000000000019abf4 /system/vendor/lib64/egl/libGLESv2_adreno.so (_ZNK12EglFenceSync15ObjGetAttributeEiPi+52)

#04 pc 000000000019407c /system/vendor/lib64/egl/libGLESv2_adreno.so (_ZN6EglApi13GetSyncAttribEPvS0_iPi+124)

#05 pc 0000000000009bf8 /system/vendor/lib64/egl/libEGL_adreno.so (eglGetSyncAttribKHR+56)

#06 pc 0000000000017088 /system/lib64/libEGL.so (eglGetSyncAttribKHR+124)

#07 pc 000000000103b328 /data/app/com.android.chrome-1/base.apk

backtrace:

#00 pc 00000000001ca8b8 /system/vendor/lib64/egl/libGLESv2_adreno.so (_ZN9EsxGfxMem15UpdateTimestampEPK10EsxContext13EsxAccessTypeP20EsxBucketIdReference+184)

#01 pc 00000000001b9810 /system/vendor/lib64/egl/libGLESv2_adreno.so (_ZN9EsxCmdMgr16GfxMemReferencedEP9EsxGfxMem13EsxAccessType+48)

#02 pc 0000000000172980 /system/vendor/lib64/egl/libGLESv2_adreno.so (_ZN11EsxResource21UpdateGfxMemReferenceEP9EsxCmdMgrj13EsxAccessType+64)

#03 pc 0000000000294cc0 /system/vendor/lib64/egl/libGLESv2_adreno.so (_ZN10A5xContext22WriteRenderTargetStateE13EsxCmdBufTypeji+544)

#04 pc 000000000029696c /system/vendor/lib64/egl/libGLESv2_adreno.so (_ZN10A5xContext13ValidateStateEPK17EsxDrawDescriptor+2412)

#05 pc 0000000000296f30 /system/vendor/lib64/egl/libGLESv2_adreno.so (_ZN10A5xContext18HwValidateGfxStateEPK17EsxDrawDescriptor+16)

#06 pc 00000000001160a0 /system/vendor/lib64/egl/libGLESv2_adreno.so (_ZN10EsxContext16ValidateGfxStateEPK17EsxDrawDescriptor+768)

#07 pc 0000000000108444 /system/vendor/lib64/egl/libGLESv2_adreno.so (_ZN10EsxContext19DrawArraysInstancedE11EsxPrimTypeijj+164)

#08 pc 00000000000dcb6c /system/vendor/lib64/egl/libGLESv2_adreno.so (glDrawArrays+108)

#09 pc 0000000002437e34 /data/app/com.android.chrome-2/base.apk

Maybe it's related to this issue:

https://groups.google.com/forum/#!topic/google-admob-ads-sdk/I6giN0VbVa0

But it's not updating anymore.  Are you still working on this problem?

[mobileadssdk-a...@google.com]

Hi there,

Thanks for reporting this. Can you confirm which versions of chromium you are seeing this on? Please share more microdump especially from version m63 and m64 which would be very helpful in the investigation process. The WebView team is investigating all microdumps as we relay them. I would suggest that you continue the discussion on this thread as it would be easy for us to track the issue.

Regards,

Deepika Uragayala

Mobile Ads SDK Team

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

[邱至民]

So these two issues are basically the same problem?

mobileadssdk-a...@google.com於 2018年2月28日星期三 UTC+8上午4時35分06秒寫道：

[mobileadssdk-a...@google.com]

Hi there,

If you are having issues similar to the issue reported in this thread, please continue your communication on the same thread where crashes for the SIGTRAP exception are reported . It is still being investigated by the WebView Team and we will update the thread if we have any updates on the issue. 

If your issue is about something else, please open a new thread and we will look into the issue and assist you further.

Regards,

Deepika Uragayala

Mobile Ads SDK Team

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

[Andrey T]

Have more than 530 during last week with the same crash reports in the google play console, but I was not able to reproduce the problem on my side  

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)

pid: 0, tid: 0 >>> com.app.id <<< backtrace:

#00 pc 00000000006b0894 /data/app/com.android.chrome-6sjNIm8JOoB8de6zQaPl8w==/base.apk

#01 pc 00000000006acc28 /data/app/com.android.chrome-6sjNIm8JOoB8de6zQaPl8w==/base.apk

Started occur after 04.12.2018 when chrome v71.0.3578 was released on android devices.

Any suggestions how it could be resolved? Or ways to retrieve more data about the crash from the user devices?

[mobileadssdk-a...@google.com]

Hi there,

Can you please share the complete logs for us to take a look? Can you confirm which versions of chromium you are seeing this on? Please share more microdump which would be very helpful in the investigation process.

Regards,

Deepika Uragayala

Mobile Ads SDK Team

~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

On 12/24/18 04:06:22 a...@iagentur.ch wrote:

Have more than 530 the same crash reports in the google play console, but I was not able to reproduce the problem on my side  

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)

pid: 0, tid: 0 >>> com.app.id <<< backtrace:

#00 pc 00000000006b0894 /data/app/com.android.chrome-6sjNIm8JOoB8de6zQaPl8w==/base.apk

#01 pc 00000000006acc28 /data/app/com.android.chrome-6sjNIm8JOoB8de6zQaPl8w==/base.apk

Started occurs more frequently after 04.12.2018 when chrome v71.0.3578 was released on android devices.

[Konstantin T]

Same happens to me. Many crashes with "Backtrace" like this one (not usable at all):

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)

base.apk

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** pid: 0, tid: 0 >>> app.id <<< backtrace:

#00 pc 00000000006b0894 /data/app/com.android.chrome-IY7Fj-YCk01c3qp6j9LuMA==/base.apk

#01 pc 00000000006acc28 /data/app/com.android.chrome-IY7Fj-YCk01c3qp6j9LuMA==/base.apk

Happens mostly on 8.0 and 8.1 devices.

[mobileadssdk...@google.com]

Hello there,

Thanks for reaching out to us. Our team has already shared this with Android Chrome team and they are investigating the issue. What we heard from the team is that they will investigate and roll-out fixes to Android WebView as required. 

Regards,
Deepika Uragayala
Mobile Ads SDK Team

=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

Also find us on our blog and Google+ page:
    http://googleadsdeveloper.blogspot.com
    https://plus.google.com/115658573333388777174/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~