Adding appropriate components and related people in Cc for further inputs.
Thank You.

It's very difficult to determine what's causing the issue with just that information.

1) Ideally we need the logcat output from the crash (which will contain a large hex-encoded crash dump between lines that say BEGIN BREAKPAD MICRODUMP and END BREAKPAD MICRODUMP), to get the actual stack trace.

2) Failing that, the tiny amount of crash data there is sometimes useful but only if we know what version of WebView the user was using, to look up the address reliably.

3) You didn't include the name of your app, which makes it impossible for us to look for other crashes being reported in it or attempt to reproduce any issues.

Thank you for your reply, I understand my report not being very useful. I was able to reduce the amount of crashes we were getting by rolling back or disabling WebView on problematic devices (i was never able to replicate the problem myself). Since then it has not been a consistent issue and hence I am unable to give you any further information other than that the apps name is FireMate Mobile.

If I do notice this happening again I will try to get more specific information and go from there.

Thanks again.

Thank you for providing more feedback. Adding requester "torne@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

"FireMate Mobile" isn't terribly helpful, unfortunately. For future reference, a full package name (e.g. com.android.chrome) would be great. And, like Torne mentioned, we really need the device logcat (specifically, the microdump).

I'll close this since we don't have enough info to debug, but please comment on this issue if you start seeing more crashes or can get us more information.

"FireMate Mobile" doesn't return any search results on the play store, so yeah, we need the actual package name. If you tell us that, we can check for crash data and see if anything looks unusual.

Sorry, I was not expecting another reply because of inadequate information and the ticket being closed. The package is au.com.firemate.firematemobile if you want to take a look, otherwise I will make sure I provide better details next time.

Cheers

We only have one crash in that app reported (though it's on the same type of device as the one you pasted above, but on a different OS version and quite an old webview). The crash in our db is an out-of-memory error while executing JS code. It's likely that your crashes are that.

Awesome. That is very handy information and no real surprise.

Thank you again.