Hello,
We are finding that after a prolonged period of play in our game, the app tends
to crash with a stack trace similar to:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'google/occam/mako:4.4.4/KTU84P/1227136:user/release-keys'
Revision: '11'
pid: 15960, tid: 16501, name: BrowserBlocking >>> com.example.app <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
r0 00000000 r1 00004075 r2 00000006 r3 00000000
r4 00000006 r5 00000002 r6 00004075 r7 0000010c
r8 7fb67880 r9 00008000 sl 917374f8 fp 782e5908
ip 00000000 sp 915f7808 lr 40101fe5 pc 40110f90 cpsr 000f0010
d0 74726f6261204d56 d1 000000000000006e
d2 0000000000000075 d3 000000000000006c
d4 42d9e68042a416d8 d5 42f1557842f3b310
d6 4366b0404366a028 d7 4348b1a8437ccc00
d8 0000000000000000 d9 0000000000000000
d10 0000000000000000 d11 0000000000000000
d12 0000000000000000 d13 0000000000000000
d14 0000000000000000 d15 0000000000000000
d16 3f802fb6d7685c16 d17 3fe62e42fee00000
d18 4000000000000000 d19 bfb697e1f2b37500
d20 3fc5549fdf07f644 d21 bf66c05793e56101
d22 bfb6ecf2aa367267 d23 40f0000000000000
d24 3f6efc3ffa0d967c d25 bf6efc3e566ea324
d26 4025931319798d6e d27 4000000000000000
d28 4000b7679551b393 d29 3fb59fffffffffe7
d30 3ff0000000000000 d31 40ed4c0000000003
scr 20000012
backtrace:
#00 pc 00021f90 /system/lib/libc.so (tgkill+12)
#01 pc 00012fe1 /system/lib/libc.so (pthread_kill+48)
#02 pc 000131f5 /system/lib/libc.so (raise+10)
#03 pc 00011f2b /system/lib/libc.so
#04 pc 00021844 /system/lib/libc.so (abort+4)
#05 pc 00045cc7 /system/lib/libdvm.so (dvmAbort+78)
#06 pc 0004913f /system/lib/libdvm.so
#07 pc 00049bcf /system/lib/libdvm.so
#08 pc 001d9bf9 /data/app-lib/com.example.app-1/libxwalkcore.so
code around pc:
40110f70 e8bd00f0 e3700a01 912fff1e e2600000
40110f80 ea006d81 e92d50f0 e3a07f43 ef000000
40110f90 e8bd50f0 e3700a01 912fff1e e2600000
40110fa0 ea006d79 e92d50f0 e3a070ee ef000000
40110fb0 e8bd50f0 e3700a01 912fff1e e2600000
40110fc0 ea006d71 f200429a bf008069 f040f891
40110fd0 4001e92d d3412a10 0300f1c0 030ff013
40110fe0 eba2d01d ea5f0203 bf447cc3 eb01f811
40110ff0 eb01f800 f811bf21 f811cb01 f800eb01
40111000 f800cb01 ea5feb01 da037c43 030df9a1
40111010 031df980 f921d303 f900070d 3a40071d
40111020 f921d30b f921020d f891420d 3a40f100
40111030 022df900 422df900 3220d2f3 f921d305
40111040 f1a2020d f9000220 f102022d f0120220
40111050 d0030f10 0a0df921 0a2df900 7c42ea5f
40111060 f921d303 f900070d da03070d 030df9a1
code around lr:
40101fc4 447b4b13 42b3e010 6a1ed10e 44784811
40101fd4 ec84f7fb ea0ef00d 46224631 efd0f00e
40101fe4 d00a3001 e00b2400 2b00681b 480ad1eb
40101ff4 44782403 ec72f7fb f001e002 6804fa23
40102004 fa20f001 46206005 bf00bd70 0003b3de
40102014 0003b3d2 0003b3ca 0003b3a6 bf7ef7ff
40102024 4a3e4b3d e92d447b b08b43f0 4606589c
40102034 6823460d 930946a1 fa04f001 8000f8d0
40102044 d0482d00 f00f4628 280fff9b d8444604
40102054 ffe4f7ff d1064286 4629200f e8d8f00d
40102064 d03c2800 482ee02e f7fb4478 482debb6
40102074 e0154478 d11342b0 482b6a06 f7fb4478
40102084 4a2aec2e 46332120 a801447a f83af013
40102094 a8012101 fb54f01a 46061c42 e011d104
401020a4 28006800 e02cd1e6 46294630 f00d4622
401020b4 1c43e914 d11e4607 f9c4f001 29046801
There is no exception along with this native crash but right before the
application crashes there is usually another stack similar to:
12-16 16:07:12.614 E/dalvikvm(10451): JNI ERROR (app bug): local reference
table overflow (max=512)
12-16 16:07:12.614 W/dalvikvm(10451): JNI local reference table (0x9be63090)
dump:
12-16 16:07:12.614 W/dalvikvm(10451): Last 10 entries (of 512):
12-16 16:07:12.614 W/dalvikvm(10451): 511: 0x430c04f8 byte[] (4096
elements)
12-16 16:07:12.614 W/dalvikvm(10451): 510: 0x431241e8 byte[] (4096
elements)
12-16 16:07:12.614 W/dalvikvm(10451): 509: 0x43115f68 byte[] (4096
elements)
12-16 16:07:12.614 W/dalvikvm(10451): 508: 0x43114f50 byte[] (4096
elements)
12-16 16:07:12.614 W/dalvikvm(10451): 507: 0x43113f38 byte[] (4096
elements)
12-16 16:07:12.614 W/dalvikvm(10451): 506: 0x43112f20 byte[] (4096
elements)
12-16 16:07:12.614 W/dalvikvm(10451): 505: 0x43110ef0 byte[] (4096
elements)
12-16 16:07:12.614 W/dalvikvm(10451): 504: 0x4310eec0 byte[] (4096
elements)
12-16 16:07:12.614 W/dalvikvm(10451): 503: 0x43f00408 byte[] (4096
elements)
12-16 16:07:12.614 W/dalvikvm(10451): 502: 0x43eff3f0 byte[] (4096
elements)
12-16 16:07:12.614 W/dalvikvm(10451): Summary:
12-16 16:07:12.614 W/dalvikvm(10451): 512 of byte[] (4096 elements) (512
unique instances)
12-16 16:07:12.614 E/dalvikvm(10451): Failed adding to JNI local ref table (has
512 entries)
12-16 16:07:12.614 I/dalvikvm(10451): "Thread-765" prio=5 tid=49 RUNNABLE
12-16 16:07:12.614 I/dalvikvm(10451): | group="main" sCount=0 dsCount=0
obj=0x42a046a8 self=0x79830cb0
12-16 16:07:12.614 I/dalvikvm(10451): | sysTid=10899 nice=0 sched=0/0
cgrp=apps handle=2039269464
12-16 16:07:12.614 I/dalvikvm(10451): | state=R schedstat=( 801050058
682727472 6188 ) utm=29 stm=51 core=1
12-16 16:07:12.614 I/dalvikvm(10451): at dalvik.system.NativeStart.run(Native
Method)
12-16 16:07:12.614 I/dalvikvm(10451):
12-16 16:07:12.619 E/dalvikvm(10451): VM aborting
Are there any tips for debugging this type of problem? We are finding that it
generally occurs after 20-40 minutes of play. We are currently using Crosswalk
10.39.235.11.
Thanks in advance for your help!
_______________________________________________
Crosswalk-help mailing list
[email protected]
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-help
