WebView native crash on Android (libwebviewchromium.so)
Reported by
jetison...@gmail.com,
Mar 23 2017
|
||
Issue description
Steps to reproduce the problem:
N/A
What is the expected behavior?
N/A
What went wrong?
Crashes
Did this work before? N/A
Does this work in other browsers? N/A
Chrome version: 57.0.2987.110 Channel: n/a
OS Version: 10.0
Flash Version:
I'm getting this crash reported on my app:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'samsung/kltexx/klte:6.0.1/MMB29M/G900FXXS1CQAV:user/release-keys'
Revision: '14'
ABI: 'arm'
pid: 19085, tid: 10166, name: Chrome_InProcRe >>> com.faultexception.reader <<<
signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr 0xa1f98774
r0 00000148 r1 00000000 r2 00800000 r3 a1e5ad6b
r4 9bf9b000 r5 00000001 r6 a279f62c r7 99b3ddac
r8 99b3e554 r9 99b3e758 sl a279f62c fp 00000001
ip a2c0dcb4 sp 99b3dcd8 lr a1231c5b pc a1f98774 cpsr 28030030
backtrace:
#00 pc 019fa774 /data/app/com.google.android.webview-1/lib/arm/libwebviewchromium.so
There's also one at 018ffbe8:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'samsung/gt58wifixx/gt58wifi:5.0.2/LRX22G/BareBonesTouchWiz:user/release-keys'
Revision: '4'
ABI: 'arm'
pid: 4522, tid: 4577, name: Chrome_InProcRe >>> com.faultexception.reader <<<
signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr 0xa62d3be8
r0 000000d8 r1 00000000 r2 00800000 r3 a619a3b3
r4 b7cac390 r5 00000001 r6 a6a928b8 r7 b7cac3a0
r8 a00b7e04 r9 a00b8008 sl 00000001 fp a6a928b8
ip a6ee2cc0 sp a00b76c8 lr a55b609b pc a62d3be8 cpsr 08030030
backtrace:
#00 pc 018ffbe8 /data/app/com.google.android.webview-1/lib/arm/libwebviewchromium.so
Sorry I can't give the full microdump because it's on the Play Store crash report.
My app package is com.faultexception.reader.
Thanks.
,
Mar 23 2017
jetison.24@: please file a new bug using the "WebView bugs" template (it requests the data necessary to diagnose issues). If you can, please attach an apk with which to reproduce the issue. Thanks!
,
Mar 24 2017
How do I create a new issue with a template? When I go through the new issue button I don't see a "WebView bugs" option. Also, I don't know how to reproduce the bug. It was reported via the Play Store crash reports and I saw you guys could look up the crash via a backend to get more details if I posted it here.
,
Mar 24 2017
Hm. The wizard doesn't offer that choice :( https://crbug.com/new does though.. weird. We can't reliably look up a crash from that information; we can only guess by looking at crashes in the app and seeing if anything sticks out.
,
Mar 24 2017
There's 22 crashes in our db for your app; none of them look particularly unusual. Almost all of them are either out-of-memory conditions, or your app's implementation of the shouldInterceptRequest callback throwing an uncaught Java exception.
,
Mar 24 2017
The first one you list isn't in our db (no crashes with that build fingerprint) - maybe too old, we don't keep data for very long. The second one is an OOM.
,
Mar 25 2017
Thanks! |
||
►
Sign in to add a comment |
||
Comment 1 by candr...@chromium.org
, Mar 23 2017