View Single Post
Old 11-07-2021, 08:34 PM   #2
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
That sounds like a sickel triggered reboot. Sickel is a process watcher on the Kobo devices and reboots the device if something hangs. This can happen when opening larger complicated books. And I'd be pretty sure that book would fall into that category. Because this is related to what the kepub renderer does when opening a book, it is possible that it might open on the second, third or later time you try. And after that it will open with no issues.

Other than that, without seeing the book and the code in it, I can't say for sure.
davidfor is offline   Reply With Quote