Getting webvew/chromium crashes reported in play console
Reported by
mih...@gmail.com,
Jul 19
|
||||
Issue descriptionSteps to reproduce the problem: The application is Globus (bundle ch.globus) and available on play store. These crashes happen to some devices. Can't reproduce but AFAIK you have more detailed webview dump in play console than me. I hope you can take a look at that dumps and figure out what could be a problem. Usually a problem looks like: #00 pc 000000000006b354 /system/lib64/libc.so (tgkill+8) #01 pc 000000000001dbd0 /system/lib64/libc.so (abort+88) #02 pc 000000000097c244 /data/app/com.android.chrome-DNkgNjFFBXuX58ZWfW8msQ==/base.apk And since I don't have a repro case nor context what triggers it I have no idea where the problem is. What is the expected behavior? Not crashing. What went wrong? Crashes in WebView. Did this work before? No Does this work in other browsers? N/A Chrome version: Channel: stable OS Version: Flash Version: I'm reporting here since this is the suggestion from this thread https://groups.google.com/a/chromium.org/forum/#!topic/android-webview-dev/xaFmw9b6GAU
,
Jul 20
> AFAIK you have more detailed webview dump in play console than me. This isn't necessarily true, what torne@ said was > When apps crash in WebView there is a special WebView dump in the logs which, if the crash is reported to the Play Store, we can decode and analyse. We can look up the crash dumps coming from your app and see if it's a know issue. So we still need you provide us the bug report/log from play store, we could look for the special WebView dump in that log, then decode and analyse. The 3 lines of crash stack isn't telling us useful information. Please attach the log.
,
Jul 25
Shimi, unfortunately that's not the case - the information the reporter has provided here is *all there is* in the Play Store. The only thing we can do is, given the application name, look up *all* crash dumps for that application and see if we see anything interesting/out of the ordinary. We cannot easily find any *specific* crash that a developer sees in the play store as there's not any straightforward way to crossreference them. There are only three crashes for that app in the db at the moment - they are all cases where WebView called the application's WebViewClient.shouldInterceptRequest callback and the callback threw an exception, which would be an application bug. The stack fragment in this bug that calls abort() is indeed what would happen if that were the case (though it would look the same for a bunch of other things too), so that's probably the issue you are looking for.
,
Jul 25
Oh, Shimi wasn't cc'ed. See my comment #3 for future bugs like this.
,
Jul 25
Guys, " they are all cases where WebView called the application's WebViewClient.shouldInterceptRequest callback and the callback threw an exception" this is like gold to me - thank you very much. Not sure if I understand how to get a log from play store. All I see is that call stack. If something similar happens in future - what should I do (send you)?
,
Jul 25
You cannot get logs from the play store - Shimi was mistaken, the callstack you see is all you get. |
||||
►
Sign in to add a comment |
||||
Comment 1 by dtapu...@chromium.org
, Jul 20Components: Mobile>WebView