Native Crash on arm64-v8a Android 7.0 about android-spatialite

[harry-wilson]

@femski my application also crashes on Samsung tab S2. Has the problem resolved?

[YaroslavRudnyk]

@femski I'm struggling the same error on Samsung Galaxy S7, Android 8.0

[sevar83]

@YaroslavRudnyk @femski do you have some test data or conditions when this crash happens?
p.s. Actually I've got an idea what is causing the problem and how to be fixed but need a test case to really validate the fix.

[YaroslavRudnyk]

@sevar83
I'm getting this error

08-19 12:42:44.739 10340 16748 20693 F libc : Fatal signal 11 (SIGSEGV), code 2, fault addr 0x7f2b6f4000 in tid 20693 (BackgroundSaver) 08-19 12:42:44.842 10340 17237 17237 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 08-19 12:42:44.842 10340 17237 17237 F DEBUG : Build fingerprint: 'samsung/heroltexx/herolte:8.0.0/R16NW/G930FXXU5ESD2:user/release-keys' 08-19 12:42:44.842 10340 17237 17237 F DEBUG : Revision: '8' 08-19 12:42:44.842 10340 17237 17237 F DEBUG : ABI: 'arm64' 08-19 12:42:44.842 10340 17237 17237 F DEBUG : pid: 16748, tid: 20693, name: BackgroundSaver >>> com.----.----.debug <<< 08-19 12:42:44.842 10340 17237 17237 F DEBUG : signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x7f2b6f4000 08-19 12:42:44.842 10340 17237 17237 F DEBUG : x0 0000007f226002fa x1 0000007f2b654eb0 x2 00000000000cf478 x3 000000000004f8a9 08-19 12:42:44.842 10340 17237 17237 F DEBUG : x4 0000000000000036 x5 0000000000000001 x6 0000000000000019 x7 0000000000000019 08-19 12:42:44.842 10340 17237 17237 F DEBUG : x8 000000000004f8a9 x9 0000000000000002 x10 0000000000000005 x11 0000000000000004 08-19 12:42:44.842 10340 17237 17237 F DEBUG : x12 00000000000000e0 x13 000000000004f8a8 x14 000000000000001f x15 0000000000003fc0 08-19 12:42:44.842 10340 17237 17237 F DEBUG : x16 000000000000d800 x17 000000000000fffd x18 000000000004f8a9 x19 0000007f52c7b200 08-19 12:42:44.842 10340 17237 17237 F DEBUG : x20 0000007f2b654eb0 x21 0000007f2b7f8588 x22 0000007f2b7f37a0 x23 0000000000000000 08-19 12:42:44.842 10340 17237 17237 F DEBUG : x24 0000000000000003 x25 00000000131ebcd8 x26 0000000000000000 x27 0000000000000000 08-19 12:42:44.842 10340 17237 17237 F DEBUG : x28 0000000000000002 x29 0000007f2b7f37f0 x30 0000007f5361a714 08-19 12:42:44.842 10340 17237 17237 F DEBUG : sp 0000007f2b654ea0 pc 0000007f5361c930 pstate 0000000080000000 08-19 12:42:44.842 10340 17237 17237 F DEBUG : 08-19 12:42:44.842 10340 17237 17237 F DEBUG : backtrace: 08-19 12:42:44.842 10340 17237 17237 F DEBUG : #00 pc 000000000007c930 /data/app/com.---.---.debug-zHKU_81HLQu6GP-ZuoHkGA==/lib/arm64/libandroid_spatialite.so (_ZN7android19utf8ToJavaCharArrayEPKcPti+216)

when inserting big geoJSON LineString, like attached one.
fault_track.zip

For converting I use this method CastToXY(GeomFromGeoJSON(?))

Data inserts into DB successfully and sometimes the error appears right after that.

[sevar83]

@YaroslavRudnyk, please try the latest develop and let me know if it fixes your issue:

implementation 'com.github.sevar83:android-spatialite:develop-SNAPSHOT'

I committed a fix for strings longer than 64K characters.

[YaroslavRudnyk]

@sevar83
Got

ERROR: Failed to resolve: com.github.sevar83:android-spatialite:develop-SNAPSHOT

on Gradle sync

[sevar83]

Got some troubles with JitPack. Would you try again?

[YaroslavRudnyk]

@sevar83 no crashes with snapshot, so I assume this as fixed ))

[sevar83]

I'm closing this. If anyone has problems I'll reopen it.