Thread: Firmware 4.8.10956
View Single Post
Old 05-02-2018, 11:01 PM   #187
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
I was able to reproduce the blank page/99% problem with my Glo last night. In general, when it happened, I had the font set to "Publisher Default" and the book set the font to something as well. I was expecting this to mean there was an embedded font, but it seems it happens when the font family is set. For example, on of the books had this:

Code:
body {
    font-family: Palatino, Malabar, Merriweather, 'Droid Serif', serif;
}
The books that failed were all the epub versions of books purchased from Kobo. And I haven't done any clean-up of the code.

I did see the problem with Georgia selected as the font, but I'm pretty sure it was only happening after opening a few books quickly. There is probably some memory leaks involved that make it more likely as you go along.

And for people who are seeing this, how many books do you have on the device? Anyone seeing it with just a few books?
davidfor is offline   Reply With Quote