Register Guidelines E-Books Today's Posts Search

Go Back   MobileRead Forums > E-Book Readers > Amazon Kindle > Kindle Developer's Corner

Notices

Reply
 
Thread Tools Search this Thread
Old 08-13-2026, 11:21 AM   #1
Frogm4n
Guru
Frogm4n ought to be getting tired of karma fortunes by now.Frogm4n ought to be getting tired of karma fortunes by now.Frogm4n ought to be getting tired of karma fortunes by now.Frogm4n ought to be getting tired of karma fortunes by now.Frogm4n ought to be getting tired of karma fortunes by now.Frogm4n ought to be getting tired of karma fortunes by now.Frogm4n ought to be getting tired of karma fortunes by now.Frogm4n ought to be getting tired of karma fortunes by now.Frogm4n ought to be getting tired of karma fortunes by now.Frogm4n ought to be getting tired of karma fortunes by now.Frogm4n ought to be getting tired of karma fortunes by now.
 
Posts: 671
Karma: 4500001
Join Date: Jul 2023
Device: Scribe 2022, OA2, PRS-350
SQLite fixed obscure 16-year old bug that caused database corruption

https://www.theregister.com/database...utages/5287004

How likely is it that this is the cause of some of the long-standing reports of weird and unexplained database corruption on Kindles? Does Amazon do a similar aggressive checkpointing? Is the WAL used?
Frogm4n is offline   Reply With Quote
Old 08-13-2026, 01:21 PM   #2
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 53,812
Karma: 181886193
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
The single user implementation used by Kindle and Kobo ereaders is unlikely to have triggered the data race bug.

To quote the SQLite documentation on the bug ( https://sqlite.org/wal.html#the_wal_reset_bug:
Quote:
The bug only affects databases in WAL mode when there are two or more database connections open on the same file, in separate threads or processes, and when those two connections attempt to write or checkpoint at the same instant.
DNSB is offline   Reply With Quote
Reply


Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Clara BW Database Corruption= Brick nanami Kobo Reader 16 01-16-2026 01:20 PM
Database corruption: fix? richorlin Library Management 7 05-21-2025 10:44 PM
Database Corruption / FW 3.5.0 PeterT Kobo Reader 7 08-26-2014 04:10 PM
Database Corruption!! Alexander Turcic Announcements 0 07-22-2003 10:08 AM


All times are GMT -4. The time now is 10:00 AM.


MobileRead.com is a privately owned, operated and funded community.