View Single Post
Old 10-21-2017, 02:50 AM   #7
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
Is the book you are talking about this one? http://www.gutenberg.org/ebooks/54658

If so, I have downloaded the no image version and it loads OK for me. But, it takes a long to open. So, I think it is the problem I was thinking of and it hasn't been completely fixed.

The problem seems to be with kepubs that are big, have a big ToC entries and long chapters. When a kepub is first opened, a word count is calculated for each chapter and stored in the database. If this takes to long, sickel can interpret this as a hang and reboot the device. For all the cases I found, when I opened the book after the reboot, the book opened. I believe this is because some of the word counts have been stored and only a few are still left to be done.

Looking at this book, it isn't particularly long, but it has over 1700 ToC entries. On my Aura ONE, that is 127 pages of ToC. And I think an extra complication is that there are multiple chapters per file. That probably makes the word count a little more complicated and takes longer.

As I said, I haven't been able to reproduce this recently. That makes me think Kobo have done something to improve the situation in 4.6.9960 and later. As you are seeing it, they probably haven't fixed it completely, but have improved the performance so that it doesn't happen as much. There are probably other dependencies such as database size and what else you have been doing.

As it is still happening for you, have you tried opening the book again after the restart?
davidfor is offline   Reply With Quote