Closed gubatron closed 7 years ago
I believe it's come up 4 times in two days now on Android 6, and it had been coming in sporadically throughout 2016
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** Build fingerprint: 'samsung/zeroflteuc/zeroflteatt:6.0.1/MMB29K/G920AUCS5DPK3:user/release-keys' Revision: '11' ABI: 'arm' pid: 23861, tid: 24564, name: Thread-1068 >>> com.frostwire.android <<< signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x4 r0 00000000 r1 00000001 r2 29ba18fe r3 00000000 r4 29ba18fe r5 00000001 r6 eb53eadc r7 00000001 r8 29ba18fd r9 29ba18fc sl df571628 fp df571580 ip dfcf5914 sp df571568 lr dfb25074 pc dfb25084 cpsr 800f0010 backtrace: #00 pc 002fb084 /data/app/com.frostwire.android-1/lib/arm/libjlibtorrent.so (_ZNSt6__ndk112__hash_tableINS_17__hash_value_typeIiiEENS_22__unordered_map_hasherIiS2_NS_4hashIiEELb1EEENS_21__unordered_map_equalIiS2_NS_8equal_toIiEELb1EEENS_9allocatorIS2_EEE4findIiEENS_15__hash_iteratorIPNS_11__hash_nodeIS2_PvEEEERKT_+68)
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** Build fingerprint: 'Verizon/hero2qltevzw/hero2qltevzw:6.0.1/MMB29M/G935VVRU4API3:user/release-keys' Revision: '15' ABI: 'arm' pid: 26619, tid: 21026, name: Thread-6135 >>> com.frostwire.android <<< signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x2403fe24 r0 726f7469 r1 00000036 r2 00000073 r3 00000159 r4 00000073 r5 0000018f r6 2403fe24 r7 00000036 r8 00000072 r9 00000072 sl 00000007 fp d5f003a8 ip de82d914 sp d5f00390 lr de65d074 pc de65d090 cpsr 200f0010 backtrace: #00 pc 002fb090 /data/app/com.frostwire.android-1/lib/arm/libjlibtorrent.so (_ZNSt6__ndk112__hash_tableINS_17__hash_value_typeIiiEENS_22__unordered_map_hasherIiS2_NS_4hashIiEELb1EEENS_21__unordered_map_equalIiS2_NS_8equal_toIiEELb1EEENS_9allocatorIS2_EEE4findIiEENS_15__hash_iteratorIPNS_11__hash_nodeIS2_PvEEEERKT_+80)
maybe a bug in android libc++, NDK r14 should be released soon, maybe the error goes away
libc++
definitely not an error in jlibtorrent or libtorrent
jlibtorrent
libtorrent
I believe it's come up 4 times in two days now on Android 6, and it had been coming in sporadically throughout 2016