Thousands of crashes started on April 8. (AwDataDirLock and Signal 11)

[AlphaInventor]

I see thousands of crashes related to the WebView from April 8 in the google play console. 

There are two types of crashes. One is AwDataDirLock and another is Signal 11.

1. From google play console, there is a crash log that occurs on Android 9 and 10. This error started on April 10. 

   I could not find this issue in this group. So I think it is a new issue.

  

  Google Pixel 3a (sargo), 3840MB RAM, Android 10
  java.lang.RuntimeException: 
    at org.chromium.android_webview.AwDataDirLock.a (PG:26)
    at v7.g (PG:46)
    at u7.run (PG:2)
    at ov.f (PG:11)
    at nv.run (Unknown Source:2)
    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:7356)
    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:930)

  Acer Liquid S1 (a10), 1024MB RAM, Android 9
  java.lang.RuntimeException: 
    at org.chromium.android_webview.AwDataDirLock.a (PG:26)
    at kn.g (PG:46)
    at jn.run (PG:2)
    at QB0.f (PG:11)
    at PB0.run (Unknown Source:2)
    at android.os.Handler.handleCallback (Handler.java:873)
    at android.os.Handler.dispatchMessage (Handler.java:99)
    at android.os.Looper.loop (Looper.java:214)
    at android.app.ActivityThread.main (ActivityThread.java:7091)
    at java.lang.reflect.Method.invoke (Native Method)
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:494)
    at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:975)

  Error message is "Using WebView from more than one process at once with the same data directory is not supported..."

  But this app does not use multi process.

  From the error message, I guess that Admob has been changed to create and use WebView in a separate process. 

  And it's causing the problem with the WebView.

  Because this problem started to happen in all previous app versions, it is not related to the update of our app. 

  I guess that it is related to the update of Google Play Service (Admob) or WebView in April.

2. Another crash that I can see on all other android version is signal 11 error. 

  signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)
    #00  pc 0000000000000000  <unknown>
    #01  pc 000000000186e213  /data/app/com.android.chrome-1/base.apk (offset 0xc07000)

  It is already famous WebView crash error. 

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

  - https://groups.google.com/forum/#!topic/google-admob-ads-sdk/I6giN0VbVa0%5B1-25%5D 

  But I read that Signal 11 or Signal 5 errors occur when using banner ads in above thread. But this app uses only native advanced ads and we have not seen these errors before April 8. So I think this is a new issue.

  I guess that this crash could be related to the above AwDataDirLock error because this error started on April 8. 

  AwDataDirLock error could be simply fixed by using WebView.setDataDirectorySuffix on Android 9 and Android 10. 

  But I hope admob team also look the side effect on older android versions like this crash.

  I could not reproduce these error in my test devices yet. But I hope the stack trace from google play console helps.

  

[Mobile Ads SDK Forum Advisor Prod]

HI AlphaInventor,

Thank you for bringing this issue to our attention.

I as wondering if you could also send us the following information.

• App Id and and Ad Unit Ids, so that we can test them
• A simple sample app of how you are implementing the SDK
• a link to your live ad so we can look at that
• any steps to repeat the crash
• Any other stack traces or error codes you might be seeing.

for the signal 11, I saw this posting that might be of some help.

Regards,
William Pescherine
Mobile Ads SDK

ref:_00D1U1174p._5004Q1zKPXD:ref

[AlphaInventor]

These problems are all related to the issues of the chrome WebView. 

Problem 1 : This is a problem that has also occurred in the past. WebView has changed code to process it in the new class AwDataDirLock . https://bugs.chromium.org/p/chromium/issues/detail?id=558377

Problem 2 : The chromium developer answered that there was a bug in the chromium 81 version and it was fixed in 83. Chrome M83 stable version is released today. I hope this information is helpful to other developers.  https://bugs.chromium.org/p/chromium/issues/detail?id=1081690 If you see Signal 11 error on low-end devices, this is the error associated with it.

I hope this infomration is helpful to other developers.

 

Thank you for your support Admob Team.

2020년 5월 6일 수요일 오후 11시 16분 36초 UTC+9, mobileadssdkforumadvisor 님의 말:

[Mobile Ads SDK Forum Advisor Prod]

Hi there,

I work along with William.

With regard to the Signal 11 issue, this is an issue that other publishers have experienced as well and 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 allow us to replicate the behavior in our test app environment by trafficking the creative in the test network.

As per AwDataDirLock error, would you able to reproduce the issue locally? If so, would it be possible for you to provide a reproducible project? This will be a big help to our investigation. Also, kindly provide us the following details as well.

• Crash rates
• Affected devices (device list and their android version)
• Full stack trace of the crash log

Regards,
Teejay Pimentel
Mobile Ads SDK Team

ref:_00D1U1174p._5004Q1zKPXD:ref

[AlphaInventor]

AWDataDirLock error is not severe. Crash rate is under 0.01%. I can ignore it. But I wrote it because it is a crash report that has started to occur after chrome M81 update and it has backtraces. I guessed that it could be related to the Signal 11 but it was not. 

I could not reproduce AWDataDirLock. But I think that chromium should not raise RuntimeException if webview_data.lock file is locked by same process name. It is not the case that app uses multiple processes explicitly. 

2020년 5월 20일 수요일 오후 3시 13분 48초 UTC+9, mobileadssdkforumadvisor 님의 말:

[Mobile Ads SDK Forum Advisor Prod]

Hi there,

Thank you for getting back to us. I've discussed this to the team and they mentioned that this appears to be an issue with chromium rather than the Mobile Ads SDK. With this, we would suggest to file a ticket on chromium issue bug instead.