Native Exception Loading Huffington Post Urls
Reported by
noah.sei...@huffingtonpost.com,
Jun 28 2016
|
|||||
Issue description
Steps to reproduce the problem:
1. Open Huffington Post
2. Select an article
3.
What is the expected behavior?
For no native exception to occur.
What went wrong?
We are receiving countless native exceptions daily from ranging from Nexus devices to common manufacturer devices. Being that the issue occurs on Nexus as well as manufacturer branded devices the issue is likely not at the Android level, it must be at the Android System Webview level. This issue was not occurring in the previous production release of the Android System Webview on the Play Store.
We are currently being inundated with technical support email, and negative feedback in the Google Play Store comments.
Being that this issue is generic (no clear steps to repro), and a native stack trace is almost useless in tracking down the root cause of the problem, it's requested to escalate the release schedule for the next production release.
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'oneplus/bacon/A0001:6.0.1/MHC19Q/ZNH2KAS1KN:user/release-keys'
Revision: '0'
ABI: 'arm'
pid: 9635, tid: 14403, name: Chrome_InProcRe >>> com.huffingtonpost.android <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
r0 93e69e90 r1 93e69dd8 r2 94228cb0 r3 00000000
r4 93e6a014 r5 93e69dd8 r6 94228c98 r7 00000000
r8 94228cb0 r9 00000018 sl 3ddaae99 fp 94369368
ip a1c14d35 sp 959f9fd0 lr a1c10d0b pc a1c13e6c cpsr 880f0030
backtrace:
#00 pc 01309e6c /data/app/com.google.android.webview-2/lib/arm/libwebviewchromium.so
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'google/hammerhead/hammerhead:6.0.1/MOB30M/2862625:user/release-keys'
Revision: '11'
ABI: 'arm'
pid: 20652, tid: 20819, name: Chrome_InProcRe >>> com.huffingtonpost.android <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
r0 9628e418 r1 9628e360 r2 9671a140 r3 00000000
r4 9628e59c r5 9628e360 r6 9671a128 r7 00000000
r8 9671a140 r9 00000030 sl 3d3a8236 fp 8faaa798
ip a4563d35 sp 97890fd0 lr a455fd0b pc a4562e6c cpsr 88030030
backtrace:
#00 pc 01309e6c /data/app/com.google.android.webview-2/lib/arm/libwebviewchromium.so
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'lge/g3_vzw/g3:6.0/MRA58K/16074094826e6:user/release-keys'
Revision: '10'
ABI: 'arm'
pid: 6044, tid: 6290, name: Chrome_InProcRe >>> com.huffingtonpost.android <<<
signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr 0x9d7f8b2a
r0 8d8bee04 r1 003ff000 r2 04638000 r3 04000000
r4 9f826c64 r5 9f8277ac r6 bc9fc000 r7 00000000
r8 00004000 r9 00000000 sl 00001000 fp 00000000
ip 9f783ae8 sp 8d8bee00 lr 9d7f8b2b pc 9d7f8b2a cpsr 28030030
backtrace:
#00 pc 00238b2a /data/app/com.google.android.webview-2/lib/arm/libwebviewchromium.so
#01 pc 00238b27 /data/app/com.google.android.webview-2/lib/arm/libwebviewchromium.so
Crashed report ID:
How much crashed? Whole browser
Is it a problem with a plugin? No
Did this work before? Yes This worked in the last production release
Chrome version: 51.0.2704.81 Channel: stable
OS Version: Android 5.0+
Flash Version: N/A
,
Jun 29 2016
Additional info. The primary complaint from user emails is a black screen then the native exception closes the application process.
,
Jun 29 2016
Hi Torne, Can you take a look at this? Please triage and prioritize as you see fit. Thanks, Peter
,
Jun 29 2016
Torne is not in, and won't be for a while, we should probably assign this to someone else. Noah, could you get a larger part of the stack traces you have pasted here? (one or two addresses might not prove useful enough).
,
Jun 29 2016
,
Jun 29 2016
Unfortunately I'm copying the entirety of the native trace available from the Play Store exceptions section. They seem short and incomplete to me as well. Since they are native I get no exception printouts or traces anywhere else other than the Play Store console.
The only other observation worth mentioning is that I'm receiving many more email complaints of a black screen before the app closes, than the total quantity of exceptions posted in the Play Store console.
Below are a bunch of copy pastes of the traces available. There's hundreds more, with the spike in activity being substantially pronounced since the last production release.
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'samsung/gts210wifixx/gts210wifi:5.1.1/LMY47X/T810XXU2BOJ1:user/release-keys'
Revision: '6'
ABI: 'arm'
pid: 10614, tid: 10754, name: Chrome_InProcRe >>> com.huffingtonpost.android <<<
signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr 0xa1c74b2a
r0 94a6c11c r1 00378000 r2 04aaa000 r3 04000000
r4 a3ca2c64 r5 00174000 r6 00000000 r7 00000000
r8 00179000 r9 94a6c1f4 sl 00173962 fp 00000000
ip a3bffae8 sp 94a6c118 lr a1c74b2b pc a1c74b2a cpsr 28030030
backtrace:
#00 pc 00238b2a /data/app/com.google.android.webview-2/lib/arm/libwebviewchromium.so
#01 pc 00238b27 /data/app/com.google.android.webview-2/lib/arm/libwebviewchromium.so
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
UUID: 811becbc-98e7-475e-82e9-9235bbb4dab3
Build fingerprint: 'Sony/D5803/D5803:6.0.1/23.5.A.0.575/1719295681:user/release-keys'
Revision: '0'
ABI: 'arm'
pid: 21960, tid: 22106, name: Chrome_InProcRe >>> com.huffingtonpost.android <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
r0 968079a0 r1 96807b24 r2 00000000 r3 990f5028
r4 96807b24 r5 00000000 r6 00000001 r7 000000ea
r8 3e93c9fa r9 00000001 sl 3e93c9fa fp 96e2fbd0
ip a37872e9 sp 990f5010 lr a37861fd pc a37861fc cpsr 880e0030
backtrace:
#00 pc 0123a1fc /data/app/com.google.android.webview-2/lib/arm/libwebviewchromium.so
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'lge/g3_vzw/g3:6.0/MRA58K/16074094826e6:user/release-keys'
Revision: '10'
ABI: 'arm'
pid: 24232, tid: 24660, name: Chrome_InProcRe >>> com.huffingtonpost.android <<<
signal 4 (SIGILL), code 1 (ILL_ILLOPC), fault addr 0x9de74148
r0 8e47de34 r1 0074d000 r2 02f69000 r3 02000000
r4 9f60c470 r5 00748000 r6 00000000 r7 00000000
r8 0074d000 r9 9f609f74 sl 00748000 fp 6b8cc000
ip 9f578ae4 sp 8e47de30 lr 9de74149 pc 9de74148 cpsr 280e0030
backtrace:
#00 pc 00934148 /data/app/com.google.android.webview-2/lib/arm/libwebviewchromium.so
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
UUID: 197b9ca1-4feb-45ea-b205-b8392d6f922d
Build fingerprint: 'Sony/D5803/D5803:6.0.1/23.5.A.0.570/260291279:user/release-keys'
Revision: '0'
ABI: 'arm'
pid: 18427, tid: 18565, name: Chrome_InProcRe >>> com.huffingtonpost.android <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
r0 97688328 r1 97688270 r2 97a2e600 r3 00000000
r4 976884ac r5 97688270 r6 97a2e5e8 r7 00000000
r8 97a2e600 r9 00000073 sl 3f76864b fp 97b570b8
ip a38d1db5 sp 990ba020 lr a38cdd8b pc a38d0eec cpsr 88070030
backtrace:
#00 pc 01309eec /data/app/com.google.android.webview-2/lib/arm/libwebviewchromium.so
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
UUID: 31504650-67b2-498c-b15f-f0b99685e503
Build fingerprint: 'Sony/D5503/D5503:5.1.1/14.6.A.1.236/2031203603:user/release-keys'
Revision: '0'
ABI: 'arm'
pid: 31038, tid: 31197, name: Chrome_InProcRe >>> com.huffingtonpost.android <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
r0 5a4891c0 r1 5a489344 r2 00000000 r3 9a7ff458
r4 5a489344 r5 00000000 r6 00000001 r7 0000001a
r8 3f289316 r9 00000001 sl 3f289316 fp 97d65b60
ip a94082e9 sp 9a7ff440 lr a94071fd pc a94071fc cpsr 88030030
backtrace:
#00 pc 0123a1fc /data/app/com.google.android.webview-2/lib/arm/libwebviewchromium.so
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'samsung/a5xeltexx/a5xelte:5.1.1/LMY47X/A510FXXS2APD2:user/release-keys'
Revision: '4'
ABI: 'arm'
pid: 28762, tid: 29507, name: Chrome_InProcRe >>> com.huffingtonpost.android <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
r0 571947a8 r1 5719492c r2 00000000 r3 d88fb4a8
r4 5719492c r5 00000000 r6 00000001 r7 00000023
r8 3f54f3aa r9 00000001 sl 3f54f3aa fp d6679710
ip e46ec2e9 sp d88fb490 lr e46eb1fd pc e46eb1fc cpsr 880e0030
backtrace:
#00 pc 0123a1fc /data/app/com.google.android.webview-2/lib/arm/libwebviewchromium.so
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'google/hammerhead/hammerhead:6.0.1/MOB30H/2751534:user/release-keys'
Revision: '11'
ABI: 'arm'
pid: 12581, tid: 12775, name: Chrome_InProcRe >>> com.huffingtonpost.android <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
r0 948313c0 r1 94831544 r2 00000000 r3 98379fd8
r4 94831544 r5 00000000 r6 00000001 r7 00000085
r8 3f33cec8 r9 00000001 sl 3f33cec8 fp 94d79ed8
ip a45092e9 sp 98379fc0 lr a45081fd pc a45081fc cpsr 880b0030
backtrace:
#00 pc 0123a1fc /data/app/com.google.android.webview-2/lib/arm/libwebviewchromium.so
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'samsung/s5neoltexx/s5neolte:5.1.1/LMY47X/G903FXXU1AOI5:user/release-keys'
Revision: '0'
ABI: 'arm'
pid: 28135, tid: 28293, name: Chrome_InProcRe >>> com.huffingtonpost.android <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
r0 d4d45848 r1 d4d459cc r2 00000000 r3 d8ef5458
r4 d4d459cc r5 00000000 r6 00000001 r7 0000005d
r8 3cb8d60a r9 00000001 sl 3cb8d60a fp d62774b0
ip e40c92e9 sp d8ef5440 lr e40c81fd pc e40c81fc cpsr 880b0030
backtrace:
#00 pc 0123a1fc /data/app/com.google.android.webview-2/lib/arm/libwebviewchromium.so
,
Jun 29 2016
Here's one from June 27'th that's a bit more lengthy.
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'samsung/klteuc/klteatt:5.0/LRX21T/G900AUCU4BOF3:user/release-keys'
Revision: '14'
ABI: 'arm'
pid: 32036, tid: 32195, name: CompositorTileW >>> com.huffingtonpost.android <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x8
r0 00000000 r1 ffffffff r2 00000002 r3 8fdde9d8
r4 954ffa54 r5 8fdced30 r6 954ffa60 r7 954ffa78
r8 8f7ac588 r9 aee50f60 sl 954ffa54 fp b6fb4e04
ip 97734300 sp 954ffa38 lr a3d395cb pc a3eb0d80 cpsr 800f0030
backtrace:
#00 pc 0042fd80 /data/app/com.google.android.webview-1/lib/arm/libwebviewchromium.so
ptrace attach to 32036 failed: Operation not permitted
ptrace attach to 32042 failed: Operation not permitted
ptrace attach to 32044 failed: Operation not permitted
ptrace attach to 32045 failed: Operation not permitted
ptrace attach to 32046 failed: Operation not permitted
ptrace attach to 32047 failed: Operation not permitted
ptrace attach to 32048 failed: Operation not permitted
ptrace attach to 32049 failed: Operation not permitted
ptrace attach to 32050 failed: Operation not permitted
ptrace attach to 32056 failed: Operation not permitted
ptrace attach to 32058 failed: Operation not permitted
ptrace attach to 32059 failed: Operation not permitted
ptrace attach to 32060 failed: Operation not permitted
ptrace attach to 32061 failed: Operation not permitted
ptrace attach to 32062 failed: Operation not permitted
ptrace attach to 32063 failed: Operation not permitted
ptrace attach to 32064 failed: Operation not permitted
ptrace attach to 32067 failed: Operation not permitted
ptrace attach to 32070 failed: Operation not permitted
ptrace attach to 32077 failed: Operation not permitted
ptrace attach to 32078 failed: Operation not permitted
ptrace attach to 32082 failed: Operation not permitted
ptrace attach to 32085 failed: Operation not permitted
ptrace attach to 32093 failed: Operation not permitted
ptrace attach to 32094 failed: Operation not permitted
ptrace attach to 32095 failed: Operation not permitted
ptrace attach to 32097 failed: Operation not permitted
ptrace attach to 32099 failed: Operation not permitted
ptrace attach to 32100 failed: Operation not permitted
ptrace attach to 32101 failed: Operation not permitted
ptrace attach to 32102 failed: Operation not permitted
ptrace attach to 32103 failed: Operation not permitted
ptrace attach to 32104 failed: Operation not permitted
ptrace attach to 32105 failed: Operation not permitted
ptrace attach to 32106 failed: Operation not permitted
ptrace attach to 32107 failed: Operation not permitted
ptrace attach to 32108 failed: Operation not permitted
ptrace attach to 32109 failed: Operation not permitted
ptrace attach to 32114 failed: Operation not permitted
ptrace attach to 32117 failed: Operation not permitted
ptrace attach to 32121 failed: Operation not permitted
ptrace attach to 32129 failed: Operation not permitted
ptrace attach to 32130 failed: Operation not permitted
ptrace attach to 32133 failed: Operation not permitted
ptrace attach to 32135 failed: Operation not permitted
ptrace attach to 32139 failed: Operation not permitted
ptrace attach to 32142 failed: Operation not permitted
ptrace attach to 32143 failed: Operation not permitted
ptrace attach to 32149 failed: Operation not permitted
ptrace attach to 32150 failed: Operation not permitted
ptrace attach to 32151 failed: Operation not permitted
ptrace attach to 32156 failed: Operation not permitted
ptrace attach to 32157 failed: Operation not permitted
ptrace attach to 32159 failed: Operation not permitted
ptrace attach to 32161 failed: Operation not permitted
ptrace attach to 32162 failed: Operation not permitted
ptrace attach to 32163 failed: Operation not permitted
ptrace attach to 32164 failed: Operation not permitted
ptrace attach to 32167 failed: Operation not permitted
ptrace attach to 32171 failed: Operation not permitted
ptrace attach to 32172 failed: Operation not permitted
ptrace attach to 32173 failed: Operation not permitted
ptrace attach to 32174 failed: Operation not permitted
ptrace attach to 32175 failed: Operation not permitted
ptrace attach to 32179 failed: Operation not permitted
ptrace attach to 32184 failed: Operation not permitted
ptrace attach to 32185 failed: Operation not permitted
ptrace attach to 32186 failed: Operation not permitted
ptrace attach to 32188 failed: Operation not permitted
ptrace attach to 32190 failed: Operation not permitted
ptrace attach to 32192 failed: Operation not permitted
ptrace attach to 32193 failed: Operation not permitted
ptrace attach to 32194 failed: Operation not permitted
ptrace attach to 32196 failed: Operation not permitted
ptrace attach to 32197 failed: Operation not permitted
ptrace attach to 32198 failed: Operation not permitted
ptrace attach to 32199 failed: Operation not permitted
ptrace attach to 32205 failed: Operation not permitted
ptrace attach to 32206 failed: Operation not permitted
ptrace attach to 32207 failed: Operation not permitted
ptrace attach to 32208 failed: Operation not permitted
ptrace attach to 32230 failed: Operation not permitted
ptrace attach to 32250 failed: Operation not permitted
ptrace attach to 32251 failed: Operation not permitted
ptrace attach to 738 failed: Operation not permitted
ptrace attach to 739 failed: Operation not permitted
ptrace attach to 740 failed: Operation not permitted
ptrace attach to 767 failed: Operation not permitted
ptrace attach to 817 failed: Operation not permitted
ptrace attach to 818 failed: Operation not permitted
ptrace attach to 1658 failed: Operation not permitted
ptrace attach to 1661 failed: Operation not permitted
ptrace attach to 1841 failed: Operation not permitted
ptrace attach to 1944 failed: Operation not permitted
ptrace attach to 4897 failed: Operation not permitted
ptrace attach to 5032 failed: Operation not permitted
ptrace attach to 5114 failed: Operation not permitted
ptrace attach to 5506 failed: Operation not permitted
ptrace attach to 5517 failed: Operation not permitted
ptrace attach to 5531 failed: Operation not permitted
ptrace attach to 5543 failed: Operation not permitted
ptrace attach to 5544 failed: Operation not permitted
ptrace attach to 5813 failed: Operation not permitted
ptrace attach to 5856 failed: Operation not permitted
ptrace attach to 5862 failed: Operation not permitted
ptrace attach to 5865 failed: Operation not permitted
ptrace attach to 5870 failed: Operation not permitted
ptrace attach to 5873 failed: Operation not permitted
ptrace attach to 5874 failed: Operation not permitted
ptrace attach to 5875 failed: Operation not permitted
ptrace attach to 5877 failed: Operation not permitted
ptrace attach to 5881 failed: Operation not permitted
ptrace attach to 5903 failed: Operation not permitted
ptrace attach to 5972 failed: Operation not permitted
ptrace attach to 6240 failed: Operation not permitted
ptrace attach to 6241 failed: Operation not permitted
ptrace attach to 6242 failed: Operation not permitted
,
Jun 29 2016
These traces are from from libc.so that point to libwebviewchromium.so
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'samsung/trltespr/trltespr:6.0.1/MMB29M/N910PVPU4DPE1:user/release-keys'
Revision: '12'
ABI: 'arm'
pid: 26114, tid: 26267, name: CompositorTileW >>> com.huffingtonpost.android <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Abort message: '[FATAL:memory.cc(19)] Out of memory. size=80834560
'
r0 00000000 r1 0000669b r2 00000006 r3 928f5978
r4 928f5980 r5 928f5930 r6 0000000c r7 0000010c
r8 b6d01ec0 r9 928f45ec sl 00000000 fp 04d17000
ip 00000006 sp 928f4128 lr b6cc6c09 pc b6cc8ff8 cpsr 400f0010
backtrace:
#00 pc 00041ff8 /system/lib/libc.so (tgkill+12)
#01 pc 0003fc05 /system/lib/libc.so (pthread_kill+32)
#02 pc 0001c39f /system/lib/libc.so (raise+10)
#03 pc 0001961d /system/lib/libc.so (__libc_android_abort+34)
#04 pc 00017570 /system/lib/libc.so (abort+4)
#05 pc 019c7f19 /data/app/com.google.android.webview-2/lib/arm/libwebviewchromium.so
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'lge/g3_vzw/g3:6.0/MRA58K/16074094826e6:user/release-keys'
Revision: '10'
ABI: 'arm'
pid: 28556, tid: 28724, name: CompositorTileW >>> com.huffingtonpost.android <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Abort message: '[FATAL:memory.cc(19)] Out of memory. size=80834560
'
r0 00000000 r1 00007034 r2 00000006 r3 8c4ff978
r4 8c4ff980 r5 8c4ff930 r6 0000000c r7 0000010c
r8 b6cdaec0 r9 8c4fe5ec sl 00000000 fp 04d17000
ip 00000006 sp 8c4fe128 lr b6c9fd61 pc b6ca1fdc cpsr 400f0010
backtrace:
#00 pc 00041fdc /system/lib/libc.so (tgkill+12)
#01 pc 0003fd5d /system/lib/libc.so (pthread_kill+32)
#02 pc 0001c4f3 /system/lib/libc.so (raise+10)
#03 pc 000196a5 /system/lib/libc.so (__libc_android_abort+34)
#04 pc 000175f8 /system/lib/libc.so (abort+4)
#05 pc 019c7f19 /data/app/com.google.android.webview-2/lib/arm/libwebviewchromium.so
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'samsung/gts210wifixx/gts210wifi:6.0.1/MMB29K/T810XXU2CPD9:user/release-keys'
Revision: '6'
ABI: 'arm'
pid: 31742, tid: 31994, name: CompositorTileW >>> com.huffingtonpost.android <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Abort message: '[FATAL:memory.cc(19)] Out of memory. size=80834560
'
r0 00000000 r1 00007cfa r2 00000006 r3 91200978
r4 91200980 r5 91200930 r6 0000000c r7 0000010c
r8 b6d0bec0 r9 911ff5ec sl 00000000 fp 04d17000
ip 00000006 sp 911ff128 lr b6cd1365 pc b6cd3754 cpsr 400f0010
backtrace:
#00 pc 00042754 /system/lib/libc.so (tgkill+12)
#01 pc 00040361 /system/lib/libc.so (pthread_kill+32)
#02 pc 0001ca9b /system/lib/libc.so (raise+10)
#03 pc 00019d19 /system/lib/libc.so (__libc_android_abort+34)
#04 pc 0001755c /system/lib/libc.so (abort+4)
#05 pc 019c7f19 /data/app/com.google.android.webview-2/lib/arm/libwebviewchromium.so
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'lge/g3_vzw/g3:6.0/MRA58K/16074094826e6:user/release-keys'
Revision: '10'
ABI: 'arm'
pid: 29514, tid: 29696, name: CompositorTileW >>> com.huffingtonpost.android <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
Abort message: '[FATAL:memory.cc(19)] Out of memory. size=80834560
'
r0 00000000 r1 00007400 r2 00000006 r3 8be00978
r4 8be00980 r5 8be00930 r6 0000000c r7 0000010c
r8 b6cffec0 r9 8bdff5ec sl 00000000 fp 04d17000
ip 00000006 sp 8bdff128 lr b6cc4d61 pc b6cc6fdc cpsr 400f0010
backtrace:
#00 pc 00041fdc /system/lib/libc.so (tgkill+12)
#01 pc 0003fd5d /system/lib/libc.so (pthread_kill+32)
#02 pc 0001c4f3 /system/lib/libc.so (raise+10)
#03 pc 000196a5 /system/lib/libc.so (__libc_android_abort+34)
#04 pc 000175f8 /system/lib/libc.so (abort+4)
#05 pc 019c7f19 /data/app/com.google.android.webview-2/lib/arm/libwebviewchromium.so
,
Jun 29 2016
It's notable that in the libc.so crashes the Abort Message is an out of memory.
,
Jun 29 2016
#8 are all out of memory, and are all for the same large size (80834560 bytes). Previous experience suggests that's the result of the app displaying a very large image in a WebView.
,
Jun 29 2016
I agree. I just pinged my web team lead, he mentioned that actually have a large image that's 4Mb that should be 20k. They will push to production in an hour. I'll report back to this thread asap if I receive a substantial reduction or elimination of user complaints. Thanks for the quick feedback.
,
Jun 30 2016
I believe we can close this ticket, as the cause of the native crash is clearly an out of memory. Thank you Tobias for the feedback and quick support.
,
Jun 30 2016
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by rsgav...@chromium.org
, Jun 28 2016