View Single Post
Old 09-07-2014, 12:48 AM   #4
GeoffR
Wizard
GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.GeoffR ought to be getting tired of karma fortunes by now.
 
GeoffR's Avatar
 
Posts: 3,821
Karma: 19162882
Join Date: Nov 2012
Location: Te Riu-a-Māui
Device: Kobo Glo
(If the device stops responding but resumes normal operation after a time, then it hasn't crashed.)

I have had this happen on my Glo, and it has always been associated with a book that has extremely large internal files: either extremely long chapters, or where the publisher has put multiple chapters into a single file, resulting in a very large file.

I think the issue is caused by the device getting low on memory, and some operations such as search and sort can become very slow when there is not enough memory available to cache intermediate results.

The solution in my case has been to delete the book from the device, use Calibre to split the book's internal files into smaller chunks (an epub to epub conversion will usually do this automatically), and reload the book to the device. (Don't reload the book without deleting it first, as that will cause other problems).

Sideloaded or embedded fonts with very large files could cause similar issues i think.
GeoffR is offline   Reply With Quote