View Single Post
Old 07-15-2019, 10:25 PM   #13
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by NiLuJe View Post
This is not a Kindle. I've never heard of a corrupt book causing anything untoward at runtime, except rendering/navigation issues in that specific book.

What might happen with a broken book is the importing process failing on that specific book, which you can check in the system logs. But it has a fairly obvious tell: you get the "importing content" screen on eject even when you haven't imported any new content .
There have been cases reported where after reading a particular book, the battery drains. Restart the device and reading something else, and everything is OK. Open that book, read and close it and the battery runs down.

I assume what is happening is that a process gets started for something in the book and it doesn't end. I haven't caught it happening myself, just the occasional report here. And I think a conversion in calibre fixes it. So, it is probably some bad code in the book. I don't think I've seen one recently, so it might have been fixed with other changes.
davidfor is offline   Reply With Quote