[TIMOB-24710] Android: V8 crashes on Android N
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Critical |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2017-07-26T18:56:40.000+0000 |
Affected Version/s | Release 6.0.4 |
Fix Version/s | Release 6.1.2 |
Components | Android |
Labels | android, bug, crash, merge-6.1.2 |
Reporter | Dan Tamas |
Assignee | Gary Mathews |
Created | 2017-05-19T08:25:59.000+0000 |
Updated | 2017-10-13T01:09:51.000+0000 |
Description
Hi,
With the "Vitals" panel activated I started to have a lot of reports of V8 crashing.
All of them are *ONLY* Android 7.0+
Crash logs attached.
Thank you.
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)
_ZN2v86Object3GetENS_5LocalINS_5ValueEEE
backtrace:
native: pc 00000000003a72cc /data/app/com.arvatis.motorsporttotal-1/lib/arm/libkroll-v8.so (_ZN2v86Object3GetENS_5LocalINS_5ValueEEE+8)
native: pc 00000000002c902f /data/app/com.arvatis.motorsporttotal-1/lib/arm/libkroll-v8.so (Java_org_appcelerator_kroll_runtime_v8_V8Runtime_nativeRunModule+106)
native: pc 000000000123e55d /data/app/com.arvatis.motorsporttotal-1/oat/arm/base.odex
and
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)
_ZNK2v85Array6LengthEv
backtrace:
native: pc 000000000039d3a4 /data/app/com.arvatis.motorsporttotal-2/lib/arm/libkroll-v8.so (_ZNK2v85Array6LengthEv+4)
native: pc 00000000002c934f /data/app/com.arvatis.motorsporttotal-2/lib/arm/libkroll-v8.so (Java_org_appcelerator_kroll_runtime_v8_V8Runtime_nativeDispose+58)
native: pc 000000000097d5e7 /data/app/com.arvatis.motorsporttotal-2/oat/arm/base.odex
and
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)
_ZN2v86Object18InternalFieldCountEv
backtrace:
native: pc 000000000039a87c /data/app/com.arvatis.motorsporttotal-1/lib/arm/libkroll-v8.so (_ZN2v86Object18InternalFieldCountEv+4)
native: pc 0000000000003de1 /data/app/com.arvatis.motorsporttotal-1/lib/arm/libti.ivwtracker.so (_ZN8titanium10JavaObject12isJavaObjectEN2v85LocalINS1_6ObjectEEE+2)
native: pc 0000000000003df3 /data/app/com.arvatis.motorsporttotal-1/lib/arm/libti.ivwtracker.so (_ZN8titanium5Proxy6unwrapEN2v85LocalINS1_6ObjectEEE+4)
native: pc 0000000000005b97 /data/app/com.arvatis.motorsporttotal-1/lib/arm/libti.ivwtracker.so (_ZN2ti10ivwtracker16IvwtrackerModule5trackERKN2v820FunctionCallbackInfoINS2_5ValueEEE+130)
native: pc 00000000003b7620 /data/app/com.arvatis.motorsporttotal-1/lib/arm/libkroll-v8.so (_ZN2v88internal25FunctionCallbackArguments4CallEPFvRKNS_20FunctionCallbackInfoINS_5ValueEEEE+136)
native: pc 0000000000408028 /data/app/com.arvatis.motorsporttotal-1/lib/arm/libkroll-v8.so
native: pc 0000000000408698 /data/app/com.arvatis.motorsporttotal-1/lib/arm/libkroll-v8.so
native: pc 0000000000000098 <anonymous:d1e0a000>
[~rborn] Could you provide example code that can reproduce the issue?
[~gmathews] Sadly not, it's a bug I can't reproduce it but it's reported in google play a lot.
Hi, I'm also facing the same crash on my side. backtrace: native: pc 00000000003a10d8 /data/app/com.app.id-1/lib/arm/libkroll-v8.so (_ZNK2v85Array6LengthEv+4) native: pc 00000000002ca0f7 /data/app/com.app.id-1/lib/arm/libkroll-v8.so (Java_org_appcelerator_kroll_runtime_v8_V8Runtime_nativeDispose+58) native: pc 0000000000581d8f /data/app/com.app.id-1/oat/arm/base.odex
Hi, experiencing the the same reports for a couple of weeks now: backtrace: native: pc 000000000039d464 /data/app/com.my-app.id-1/lib/arm/libkroll-v8.so (_ZNK2v85Array6LengthEv+4) native: pc 00000000002c934f /data/app/com.my-app.id-1/lib/arm/libkroll-v8.so (Java_org_appcelerator_kroll_runtime_v8_V8Runtime_nativeDispose+58) native: pc 0000000000d34c87 /data/app/com.my-app.id-1/oat/arm/base.odex
Hi, I'm seeing these error as well in the google play, please advise.
We are seeing this hundreds of times a day as well. It could be related to reopening an app after the device goes into sleep but we aren't 100% sure. We have noticed a lot more of the app stopping immediately when opening after coming out of the device being asleep.
Another log
App was in background and I started it again using the app icon. * HTC A9 * Android 7 * Ti SDK 6.1.0
master: https://github.com/appcelerator/titanium_mobile/pull/9148
What's the status on this? We're getting flooded with crash complaints tying back to this. Thanks in advance!
We're also getting a lot of crashing complaints that we've traced back to this issue. Can the solution to this be treated as a priority? Thanks.
any update on this? it's gone quiet - thanks
6_1_X: https://github.com/appcelerator/titanium_mobile/pull/9200
I seem to be getting a lot of these crashes as well, and as stated Android 7+. Thanks for this fix! Any idea why 6_1_X PR failed checks?
Has it been merged yet or not? I don't see it's Pull request yet merged into 6_1_X branch. Guys when can we expect the solution for it, We are losing our business here. If its going to take some more time, then atleast provide some work around for now.
[~speedyankur@gmail.com] The PR will be merged this week after QE-validation passed, 6.1.2 is scheduled for next week. But you can already grab the PR and append it to your existing SDK if you need it already. [~fahad86] Tests looking good for me. Something the unit-tests have timeouts, but that won't block the merge-process at all. If it helps, I can create a 6.1.2 build that includes the PR already.
Completed FR with this environment: Node Version: 6.10.3 NPM Version: 3.10.10 Mac OS: 10.12.4 Appc CLI: 6.2.2 Appc CLI NPM: 4.2.9 Titanium SDK version: 6.1.X PR-9200 Appcelerator Studio, build: 4.9.0.201705302345 Android Device 7.1.2 I was not able to reproduce the original bug, however I tested the PR by creating an app, and running adb logcat to check for error messages. I tried several things such as backing out of the app, and putting it in the background while watching the logcat window I had open. None of the originally reported errors were observed, so I am merging the ticket. I'll keep the status as "Resolved" (ie not "Closed") until confirmation that reporter of the bug does not get any more errors.
I've just build a SDK with the bugfix and still have a crash when I restart an app (default
appc new
app) that I close with the back button: [Video: Start - Close - Start -> Crash](http://migaweb.de/start_after_closing.mp4) The log:Happens almost everytime. Device: HTC A9 (7.0) SDK: 6.2.0 (master from 19.07.) *Good:* On the other hand the restart of a background app that was closed is way faster now: [Video: App running - Put to background - Start other programs - Start old app again -> Restart](http://migaweb.de/start_after_background_close.mp4) Perhaps it is working better for the other people with this problem
With 6.1.2.v20170719112744 the (start app - close it - start app again) behaviour is correct but once the app is closed when it is in background and opened up again it is slower as with 6.2.x and the "app crashed want to restart" box is shown after the restart. Log:
app is the default Alloy example when creating a new app with
appc new
6_1_X: https://github.com/appcelerator/titanium_mobile/pull/9256
Passed FR with this environment: Node Version: 6.10.3 NPM Version: 3.10.10 Mac OS: 10.12.4 Appc CLI: 6.2.2 Appc CLI NPM: 4.2.9 Titanium SDK version: 6.1.2.v20170726101856 Appcelerator Studio, build: 4.9.0.201705302345 Android 7.1.2 Closing, as changes are in SDK 6.1.2.v20170726115259
Hi Is there any possibility to backport to SDK 5.5.1? because 1 of my project which in playstore using this SDK and receiving crash report a lot due to this issue, thanks.