Issue metadata
Sign in to add a comment
|
Android app crashing in webview while navigating from one page to the other page.
Reported by
shailesh...@gmail.com,
Sep 27 2016
|
||||||||||||||||||||||
Issue description
Steps to reproduce the problem:
1. Run android Webview in hybrid app container
2. Play with the application for more than 4 mins.
3. Application crashes.
What is the expected behavior?
Application should not crash
What went wrong?
Build fingerprint: 'samsung/zenltedv/zenlte:5.1.1/LMY47X/G928IDVU2AOK1:user/release-keys'
Revision: '9'
ABI: 'arm'
pid: 1731, tid: 3547, name: Chrome_InProcRe >>> com.uob.mighty.app <<<
signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr 0xe1de672a
r0 cdcc218c r1 030cc000 r2 45827000 r3 40000000
r4 e3f74d40 r5 030c7000 r6 00000000 r7 00000000
r8 030cc000 r9 cdcc2200 sl 030c6276 fp cdcc2254
ip e1de671b sp cdcc2188 lr e1de672b pc e1de672a cpsr 28030030
d0 0000000000000000 d1 0000000000000000
d2 002f0065006c0062 d3 0063006100650072
d4 00000000000ad8ac d5 0000000000000000
d6 0000000000000028 d7 000001f40000062e
d8 3e8000003f400000 d9 0000000000000000
d10 0000000000000000 d11 0000000000000000
d12 0000000000000000 d13 0000000000000000
d14 0000000000000000 d15 0000000000000000
d16 0000000000000000 d17 0000000000000fff
d18 3fe0000000000000 d19 0000000000000000
d20 0000006100000063 d21 0000006900000074
d22 0000000000000000 d23 0000000000000000
d24 0000000000000000 d25 0000000000000000
d26 0000000000000000 d27 0000000000000000
d28 3ff0000000000000 d29 0000000000000000
d30 0000000000000000 d31 0000000000000000
scr 80000013
backtrace:
#00 pc 0025e72a /data/app/com.google.android.webview-2/lib/arm/libwebviewchromium.so
#01 pc 0025e727 /data/app/com.google.android.webview-2/lib/arm/libwebviewchromium.so
Did this work before? Yes
Chrome version: Channel: stable
OS Version: Android 5.1.1,6.0.0,7.0
Flash Version:
This is UOB Mighty mobile banking application. This is important and we are getting lot of crashes because of this issue.
https://play.google.com/store/apps/details?id=com.uob.mighty.app&hl=en
Steps to reproduce
1. Install application
2. Go to dining / deals
3. Go to Dining landing screen , go to details, come back to home screen
4. Application crashes
,
Oct 7 2016
Issue is reproducible on Nexus5X/MOB31J, Webview: 54.0.2840.50, 53.0.2785.134, 52.0.2743.98. shailesh.96@ Can you please provide you device details and provide webview version that you are using? Thanks Logs @ http://go/chrome-androidlogs1/6/650647
,
Oct 17 2016
We are getting it all devices with WebView versions mentioned as above. We are using Nexus 5, Nexus 6,Samsung s6, Samsung s7 Specifically these are 2 devices, Mozilla/5.0 (Linux; Android 6.0.1; SM-G925I Build/MMB29K; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/51.0.2704.81 Mobile Safari/537.36 Version/4.0 Chrome/52.0.2704.81 Mobile Safari/537.36 Mozilla/5.0 (Linux; Android 6.0.1; HTC_M10h Build/MMB29M; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/53.0.2785.124 Mobile Safari/537.36 can you please provide us quick workaround to avoid this crash. Appreciate your understanding in this regard. Many Thanks, Shailesh
,
Oct 17 2016
,
Oct 18 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 16 2017
We have the same issue using WebView. Our Google Play Developer Console shows that this issue exists in all recent Android os versions: 7.0, 7.1, 8.0, 8.1. All major device vendors affected (from Samsung Galaxy, through Motorola and LG ending on Nexus devices). signal 4 (SIGILL), code 1 (ILL_ILLOPC) Chrome.apk LGE LG Stylus3 (msf3), 2048MB RAM, Android 7.0 backtrace: native: pc 000000000153673c /system/app/Chrome/Chrome.apk Samsung Galaxy S7 (heroqlteatt), 4096MB RAM, Android 7.0 backtrace: native: pc 00000000020e644c /system/app/Chrome/Chrome.apk LGE Nexus 5X (bullhead), 2048MB RAM, Android 8.1 backtrace: native: pc 0000000000a2b96e /system/app/Chrome/Chrome.apk Motorola Moto X Play (lux_uds), 1024MB RAM, Android 7.1 backtrace: native: pc 00000000018601ea /system/app/Chrome/Chrome.apk Over 100 reports total, and around 20 only this week.
,
Dec 13 2017
satyavathir@ can you try to reproduce this to give the feedback that is needed here?
,
Feb 15 2018
cmasso@, Some one will try to repro and update the issue.
,
Feb 15 2018
ppolisetty@, Could you try to repro on latest M65 & M66 and update the bug.
,
Feb 16 2018
We were unable to repro the issue mentioned in #0 anymore, devices tested: Nexus5X/N2G48J, Samsung Galaxy S7 (SM-G930V)/NRD90M, Pixel 2/8.1.0 with 64.0.3282.137, 65.0.3325.78 & 66.0.3348.3. michal.brewczak@, looks like this issue is fixed, please file a new bug if you still see this issue. Please provide either a sample app or link to your app on the play store to help us with the issue. Thanks! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by rsgav...@chromium.org
, Sep 27 2016