android - Native crash at /dev/ashmem/dalvik-jit-code-cache -
i'm getting crashes numerous devices native crash android game, geoguess (https://play.google.com/store/apps/details?id=uk.co.quinny898.game.geoguess)
it's java, don't see why crash happening. crash on 34 unique devices (and counting) , causing problems users (it appears on launch)
the stack trace follows:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** build fingerprint: 'samsung/serranoltexx/serranolte:4.4.2/kot49h/i9195xxucnh5:user/release-keys' revision: '5' pid: 23657, tid: 23704, name: asynctask #1 >>> uk.co.quinny898.game.geoguess <<< signal 16 (sigstkflt), code -6 (si_tkill), fault addr -------- r0 42049ee8 r1 00000000 r2 663c69c3 r3 00000000 r4 622a880e r5 64489e8c r6 6447ca98 r7 000020f4 r8 417bbf80 r9 622a8806 sl 00000000 fp 42b5f278 ip 65c49fec sp 64861c40 lr 00000000 pc 663c69d8 cpsr 600d0030 d0 0000000000000000 d1 0000000000000000 d2 0000000000000000 d3 0000000000000000 d4 0000000000000000 d5 0000000000000000 d6 0000000000000000 d7 4140000000000000 d8 0000000000000000 d9 0000000000000000 d10 0000000000000000 d11 0000000000000000 d12 0000000000000000 d13 0000000000000000 d14 0000000000000000 d15 0000000000000000 d16 6c2f6176616a4c5b d17 64696f562f676e61 d18 577fd198577fd160 d19 577fd208577fd1d0 d20 577fd278577fd240 d21 579b81c0577fd2b0 d22 579b8230579b81f8 d23 579b82a0579b8268 d24 be5777a5d80dadae d25 3cc135bdbf311355 d26 3cc135bdbd16946f d27 3cc135bdb6c717bc d28 3ff0000000000000 d29 bef375cbdb605373 d30 be48c28772093484 d31 3fd5555555555563 scr 20000010 backtrace: #00 pc 0000e9d8 /dev/ashmem/dalvik-jit-code-cache (deleted) code around pc: 663c69b8 5897607c 65ce796c f85f0048 68010008 663c69c8 60013101 68a86829 f8d0b120 29001140 663c69d8 e001d0fa e0026029 e0056029 f8dfde00 663c69e8 6ef1003c 1c2d4788 4300e000 47806e70 663c69f8 622a8816 4300e000 47806e70 622a87b4 663c6a08 00000001 00000001 00000000 57be7128 663c6a18 002d0102 00000001 00000000 622a880e 663c6a28 65ce7970 f85f0030 68010008 60013101 663c6a38 68696928 f2c04288 1c2d8007 4300e000 663c6a48 47806e70 638d5004 f950e000 47806e70 663c6a58 638d5010 00000002 00000000 00000000 663c6a68 57c2e1f0 000a0101 00000001 00000000 663c6a78 65ce7974 f85f00bc 68010008 60013101 663c6a88 10fcf8df b1386828 f8df6800 428820f0 663c6a98 8002f000 b3984790 f8df6829 b39120d0 663c6aa8 429a680b 8009f040 8000f8d5 4008f8d8 code around lr: 00000000 ffffffff ffffffff ffffffff ffffffff 00000010 ffffffff ffffffff ffffffff ffffffff 00000020 ffffffff ffffffff ffffffff ffffffff 00000030 ffffffff ffffffff ffffffff ffffffff 00000040 ffffffff ffffffff ffffffff ffffffff 00000050 ffffffff ffffffff ffffffff ffffffff 00000060 ffffffff ffffffff ffffffff ffffffff 00000070 ffffffff ffffffff ffffffff ffffffff 00000080 ffffffff ffffffff ffffffff ffffffff 00000090 ffffffff ffffffff ffffffff ffffffff 000000a0 ffffffff ffffffff ffffffff ffffffff 000000b0 ffffffff ffffffff ffffffff ffffffff 000000c0 ffffffff ffffffff ffffffff ffffffff 000000d0 ffffffff ffffffff ffffffff ffffffff 000000e0 ffffffff ffffffff ffffffff ffffffff 000000f0 ffffffff ffffffff ffffffff ffffffff though location , fingerprint change obviously.
it's not limited android version either, being reported on 4.3 , 4.4
the devices it's being reported on follows:
xperia sp (c5303) 2 2.2% lg optimus l9 ii (l9ii) 1 1.1% galaxy s3 (d2vmu) 1 1.1% galaxy s4 mini (serranoltebmc) 2 2.2% galaxy s4 active (jactivelteatt) 1 1.1% moto x (ghost) 6 6.6% droid ultra (obake) 1 1.1% galaxy s3 (d2att) 1 1.1% lg optimus g (geehrc) 1 1.1% galaxy s4 mini (serrano3g) 1 1.1% droid mini (obakem) 1 1.1% htc 1 mini (htc_m4) 1 1.1% galaxy express2 (wilcoxlte) 1 1.1% galaxy s4 (jfltespr) 1 1.1% galaxy s4 mini (serranolte) 9 9.9% galaxy s4 (ks01lte) 2 2.2% galaxy s3 (d2vzw) 1 1.1% galaxy s4 (jfltevzw) 9 9.9% galaxy s4 (jfltecan) 1 1.1% galaxy s3 (d2usc) 1 1.1% galaxy s4 (jflteatt) 7 7.7% galaxy s4 mini (serranoltevzw) 3 3.3% htc 1 (m7) 6 6.6% galaxy s3 (d2spr) 2 2.2% galaxy note3 (hltecan) 1 1.1% xperia z (c6603) 8 8.8% galaxy s4 mini (serranolteusc) 3 3.3% galaxy tab3 7.0 (lt02ltespr) 1 1.1% galaxy note3 (hltevzw) 3 3.3% galaxy s4 (jflte) 6 6.6% droid razr m (scorpion_mini) 1 1.1% xperia tablet z (sgp321) 1 1.1% galaxy s4 (jflterefreshspr) 3 3.3% galaxy s4 (jfltetmo) 2 2.2%is can fix?
the dalvik vm throw sigstkflt @ in circumstances. can see code here. 1 such call site here. goal stack trace spinning thread debuggerd see in logcat output. (this pre-dates nice stack unwinding code android has now, , dalvik went low-maintenance mode before unwinder improved, continued use crude mechanism.)
you should see diagnostics above crash complain spinning thread -- scroll in logcat output , see find.
stack traces in jit code cache indicate thread running jit-compiled code @ time signal arrived. in other words, vm bug.
you may seeing instance of bug 58726, discussed bit in question. specific circumstances of bug supposed have been fixed 4.4.2, it's possible there's different bug similar failure characteristics. basic issue oem enhancement gone wrong... note in particular haven't seen failures on stock google nexus devices. (i think of devices in list based on qualcomm chips, point finger @ them. again.)
as noted in answer other question, workaround un-optimize code doesn't hit bad path in jit.