@ a.a.tereschenko: Could you please provide 16 digit crash id from chrome://crashes, this would help in further triaging. If there is no crash id available please provide link to app and devcie details on which this issue is seen.

Thanks!

I am not able to reproduce the crash.
The app is following
https://play.google.com/store/apps/details?id=com.phonegap.tagesanzeiger
Regarding the affected devices, see attached images

Deleted: Screen Shot 2018-12-26 at 7.16.51 PM.png 271 KB

	Screen Shot 2018-12-26 at 7.16.51 PM.png 271 KB View Download

Deleted: Screen Shot 2018-12-26 at 7.16.23 PM.png 232 KB

	Screen Shot 2018-12-26 at 7.16.23 PM.png 232 KB View Download

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I found some crash entries for your app: https://crash.corp.google.com/browse?q=product_name%3D%27AndroidWebView%27+AND+expanded_custom_data.ChromeCrashProto.webview.package_name%3D%27com.phonegap.tagesanzeiger%27

I don't see anything suspicious when I filter by M71. Specifically, I only see "content::RenderProcessHostImpl::ProcessDied" crashes (which seems plausible, given most of your crashes are on Android O, which has a separate renderer process).

All that said, I don't think there's anything we can do without a logcat. In particular, we would need to know why the renderer is crashing. I'm happy to re-open if you can provide further information though.

We are also facing tons of these crashes according to play store console. The information shown at our play store console is exactly same as provided in snapshots of OP, nothing else.
However, we are also not able to reproduce it on our android 8 and 8.1 devices. 

One thing i have noticed is, these crashes are only reported by devices running on Android 7, 8.0 and 8.1.

It'd be better if you investigate without marking it WontFix.

these crashes are only reported by devices running on Android 7 and above.

@ntfschr@chromium.org do you have any docs/info about how to detect and grab logs from such chrashes on the end users side?

> We are also facing tons of these crashes according to play store console.

What's your package name?

> The information shown at our play store console is exactly same as provided in snapshots of OP, nothing else.

Unfortunately, the 2 lines of backtrace in the original report are entirely unhelpful. That backtrace basically says "something went wrong," without giving any insight into what the core issue is. To identify the issue, we need a "microdump" from the logcat.

> It'd be better if you investigate without marking it WontFix.

First, I entirely agree that fixing is better than wont-fixing. As stated previously, this is not currently enough info to investigate, hence "wontfix." I'm happy to reopen if we can get more info, however.

> these crashes are only reported by devices running on Android 7 and above.

That's probably because Chrome is the provider on N+, but "standalone WebView" is the provider on L-M. In other words, even if the issue happened on L-M, the backtrace would not contain "/data/app/com.android.chrome..." and would be aggregated into a different bucket. Although, that's not to rule out a dependency on >= N.

> @ntfschr@chromium.org do you have any docs/info about how to detect and grab logs from such chrashes on the end users side?

That's a great question. Unfortunately, the WebView team is not familiar with the Play Console crash reporting. This might be impossible, or we might simply not know how it's done.

Our package at play store is https://goo.gl/v3Ftz8
We're not sure how to get logcat data from affected devices, I can also see so many of these reports at stackoverflow, and none of them answered.
backtrace data available at play console is not helpful in this particular case.