You need to provide the full logs, particularly the breakpad microdump (the section bracketed by ---- BEGIN BREAKPAD MICRODUMP -- with a bunch of hexdump in it). We can't symbolise the data from debuggerd usefully as the library doesn't contain unwind tables for size reasons and so the stack always stops at 2 frames.

Also, you shouldn't be using such an old webview in the first place, it's possible this is a known bug already fixed, and it's definitely not a secure version any more. You should be building the latest stable version from chromium (currently 55). The prebuilt is provided purely to have AOSP working out of the box and is not intended to be used in real builds.

We don't have the breakpad microdump, it failed every time since Android 7.0 on our platform:
01-16 18:19:23.506001  3059  3059 W google-breakpad: Microdump crash handler failed.

We know M52 is an old version, but it is the latest version Chromium released to AOSP:
https://android.googlesource.com/platform/external/chromium-webview/+/master
Is it possible to release a newer version of WebView to AOSP, or via Google Security Patch?

If breakpad doesn't work this is a critical thing to fix; you need to work out why and deal with it. We absolutely depend on breakpad to be able to debug webview crashes.

Please provide a full log so we can try to investigate what's up here, even if there's no microdump; we need to see what else happened to guess why the crash handler didn't work.

If you're building AOSP you are expected to build your own WebView from the chromium sources, not wait for a new prebuilt to be provided. See the README accompanying the prebuilts and https://www.chromium.org/developers/how-tos/build-instructions-android-webview

Actually, in this particular case you are lucky and the two frames in the debuggerd dump is enough to identify the crash: this is issue 645515, a bug in CleanupReference that causes objects to be touched after they've been destroyed. This was fixed in M54 and up. You need to use a newer version. (do not use M54, there is a bug with certificate transparency that prevents loading some popular sites; use M55, the current stable).

You need to investigate why breakpad doesn't work on your platform; this is critical. You can file a new bug about this problem with *full* logs attached and we can try to help.

Hi Torne,
Thanks for the help.
We do build our own WebView from Chromium source, but since Google Security Patch may update the AOSP WebView to newer version (CVE-2016-6754 https://source.android.com/security/bulletin/2016-11-01.html ), we think it's too risky to release our own build WebView Chromium as a Security Patch. That's the reason we use AOSP prebuilt WebView in Android 7.1.1

For the breakpad issue, we will investigate it. Thanks again.

I don't understand why that means you shouldn't release your own build of WebView. That security bulletin's WebView was just a prebuilt of the current stable version of WebView - if you had built the current stable version already yourself it would have been exactly the same and contained exactly the same security fixes. You should not wait for Google to provide you with new prebuilts, or wait for security bulletins to appear - EVERY webview update is a security update. You should keep up with the current stable version by building it yourself.

I understand, we will discuss the WebView update policy internally.
Thank you.

Hi Torne,
We found breakpad doesn't work on my Nexus 6 running Android 7.1.1
I file a new bug for the breakpad issue:
https://bugs.chromium.org/p/chromium/issues/detail?id=688252