Avoid WebView issues to completely crash our app

[Jérémy]

Hi there,

We are few developers facing a lot of crashes with "signal 5 (SIGTRAP), code 1 (TRAP_BRKPT)" / "signal 5 (SIGTRAP), code 4 (TRAP_HWBKPT)" due to AdMob and Chrome WebView.

This issue is mainly discussed here: https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/google-admob-ads-sdk/I6giN0VbVa0%5B1-25%5D

A potential fix by the Chromium team could be in progress but why don't you simply allow the app to continue even if a WebView crashed as explained here: 

https://developer.android.com/guide/webapps/managing-webview#termination-handle

MoPub has recently updated their SDK to mitigate this same issue:

Version 5.7.1 (June 3, 2019)

• Bug Fixes
• Handle WebViewClient#onRenderProcessGone for API 26+ devices so WebView crashes do not take the entire process with it. This only affects MoPub WebViews, and all WebViews in the application must handle this call in order for the process to not be killed.

Thanks.

[Mobile Ads SDK Forum Advisor Prod]

Hello Jérémy,
 
Can you please follow up on the same thread to discuss more about this issue? It will be useful for our better tracking purposes.

As requested by sam on that thread, If you are able to reproduce this locally and get the logcat output, we need a WebView microdump. This will be in the logcat on the device, please copy and attach the lines between "BEGIN BREAKPAD MICRODUMP" and "END BREAKPAD MICRODUMP" (including those 2 lines) and share it on the thread so that we will take a look into that.

Regards,
Deepika Uragayala
Mobile Ads SDK Team

 

ref:_00D1U1174p._5001UBoD8K:ref

[Jérémy]

No problem thanks.