View Single Post
Old 03-17-2022, 08:30 PM   #2428
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: 47,125
Karma: 169815798
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by DaveLessnau View Post
I'm wondering if you could test for a bad BookReader.sqlite file by watching its file size. In the one case where I noted it, the size of that file went from 15KB to 45MB when it went bad. That "bad" size was very close to the size of KoboReader.sqlite. Maybe a comparison to that would work?

Also, is there any way Kobo Utilities could be involved with the size change in BookReader.sqlite (maybe a typo)? It just seems odd that the "bad" size would be so close to the size of KoboReader.sqlite. I'm not saying it's so, I'm just wondering.
As far as I can tell from checking the KoboUtilities source, there are no references to BookReader.sqlite present.

Looking at my Sage and Clara HD, I've seen BookReader.sqlite balloon on a couple of occasions but it has always returned to it's smaller size (~875kb) while the KoboReader.sqlite has hung around 51MB on the Sage and 860MB on the Clara HD.
DNSB is offline