Alexandre Mainville wrote: > Hi, > > I am experiencing database corruption using zipvfs on android 64 > bits (x86_64). > The same program executing on 32 bits runs without problems. > > The program creates a new database on every run and does a series of > inserts and updates (always the same series of operations). > > Both programs produce the same SQLITE_DEBUG trace up until the point the 64 > bit version outputs: > zipvfs database is corrupt. Line 1100 of [9d6c1880fb] > because of a zero size payload in a slot header. > > I am waiting on a device to test behavior with arm64-v8a. > > I am using sqlite 3.8.8.3 and zipvfs 3.8.8. > > If anyone has experienced the same or has some insight on this, it would be > greatly appreciated. > > Thanks > > Alex
I'm not sure whether it's the same problem, but on our project we had memory corruptions on Android with zipvfs. The bug happened only on Android. Valgrind and asan on Linux was showing no bug. The bug turned out not to be in SQLite, but in zlib. Android was using zlib-1.2.7. After using zlib-1.2.8 instead, corruption did not happen anymore. Reading the changes in zlib-1.2.8 at http://www.zlib.net I saw: "Version 1.2.8 fixes a very rare bug in decompression. All users are encouraged to upgrade immediately." Can you check whether you use zlib-1.2.7 or zlib-1.2.8? Dominique
