Steps to reproduce the problem:
1. After a recent app update, native crashes in the WebView component have more than doubled
2. Google Play Console Crash Reports are meaningless to me because they are only one-liners of native backtrace

What is the expected behavior?

What went wrong?
We have an app that is essentially at its core driven by a WebView with a  bunch of native elements for notifications, network management, error screens etc.

Since a recent app update, the crash rate in the Play console is now noticeably above the bad behaviour threshold (and was way below before) and it's due to a sharp increase in app crashes within the WV component.

The app started to be released around the 27th of April, which unfortunately ~ coincides with the Chrome 66 rollout as far as I can see. The actual WV content (which is a customised build of a mobile web site) hasn't changed.

The crashes happen across any sdk version and vary in numbers for some of the crashes. 

Here are a few examples.

1. In this grouping above the vast majority of crashes are on 5.1 and 6.0 (about 90% in total)

---
Error: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)

Some backtrace examples (and they're all just the one line each)

  #00  pc 000000000095c240  /system/app/WebViewGoogle/lib/arm/libwebviewchromium.so (A 5.1)
  #00  pc 0000000000a38e1c  /system/app/WebViewGoogle/lib/arm/libwebviewchromium.so (A 5.1)
  #00  pc 00000000007354ae  /data/app/com.google.android.webview-1/lib/arm/libwebviewchromium.so (A 6.0)
  #00  pc 0000000000d8ed4c  /system/app/WebViewGoogle/lib/arm/libwebviewchromium.so (A 5.1)
---

2. This grouping only gets reported on Android 7+ (and the backtraces have 2 lines)

---
Error: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)

backtrace examples:

  #00  pc 000000000093ed14  /data/app/com.android.chrome-2/base.apk
  #01  pc 000000000093ecec  /data/app/com.android.chrome-2/base.apk

  #00  pc 00000000019dc9a8  /data/app/com.android.chrome-2/base.apk
  #01  pc 00000000025c9858  /data/app/com.android.chrome-2/base.apk

  #00  pc 000000000093ed14  /data/app/com.android.chrome-gxsBb6NyjjmGF0sOv4p0LQ==/base.apk
  #01  pc 000000000093ecec  /data/app/com.android.chrome-gxsBb6NyjjmGF0sOv4p0LQ==/base.apk

  #00  pc 000000000093ed14  /data/app/com.android.chrome-1/base.apk
  #01  pc 000000000093ecec  /data/app/com.android.chrome-1/base.apk
---

3. Another noticeable group is this (exclusively on Android 6)

---
Error: signal 4 (SIGILL), code 1 (ILL_ILLOPC)

backtrace samples:

  #00  pc 0000000000964520  /system/app/WebViewGoogle/WebViewGoogle.apk
  #00  pc 000000000095c240  /system/app/WebViewGoogle/WebViewGoogle.apk
  #00  pc 000000000116d2d8  /system/app/WebViewGoogle/WebViewGoogle.apk
---

Is there any way to get more info on what those backtraces actually mean and what might be behind them?

I understand that in some instances it might be the actual web content causing issues, but I've read in another, older ticket that sometimes the actual Java/Kotlin implementation of the app can cause issues, too - which I'd love to look into, but I'm just stuck at this stage.

Any suggestion, or anything else we can provide?

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: Multiple  Channel: stable
OS Version: WebView
Flash Version: