Thread: Clara crashes on epub opening
View Single Post
Old 12-31-2021, 12:29 AM   #5
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 Barruel View Post
Thanks, rtiangha.

Disabling Sickel helped a bit. My Clara tried to open the books. It stayed with a blank screen forever, but it didn't reboot, so I guess it was Sickel triggering the reboots, which is what I previously referred as "crashes".

It looks like it was indeed a RAM issue. I had 1400+ sideloaded font files. I trimmed that to ~900 and now I can load epubs.
Isn't that unwieldy? It means that there are somewhere between 250 and 900 extra lines in the fonts menu. How can you find one to use?
Quote:
It's a bit strange. Nickel, KOReader and Plato can all load books in those conditions. I expected RMSDK to be able to do the same thing.
Not strange at all. All four applications are written by different people with different requirements and different expectations. The idea that all four would work exactly the same is a lot stranger than that one wouldn't. I was told by a Kobo developer that the RMSDK was inefficient in how it loads fonts, though I would not have thought it would load all the fonts. But, maybe it is loading them to get the details so they can be used when needed. That would make sense with a sickel timeout reboot and it working when the number of fonts was reduced.

And for the record, "nickel" is the application being run for everything. It is the UI to navigate to get to the books. The kepub render was based on ACCESS. That has changed its name, but, I've lost track of what it is now called.
davidfor is offline   Reply With Quote