View Single Post
Old 09-19-2017, 07:37 AM   #24
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 compurandom View Post
I've found that some books that I've built and cause this problem cause less problems if I strip out javascript and other unnecessary stuff -- which contributes to the code complexity and size theory I think. Books (i.e., downloaded web pages) with lots of javascript cause more problems even if they are small.
Yes, any extraneous code would increase the chance of this happening.
Quote:
If it is stuffing info in the database, is there any chance the calibre kobo driver could precalculate this stuff and put it in the database instead? Maybe on a single shot basis when a book is causing issues...
I have considered that. I don't want to populate most of the database entries as I really don't know how. But, fixing this sort of thing should be pretty safe. Of course, to do that, I would have to be able to test the change. And at the moment, I can't reproduce it with the firmware I am using. Which is probably a good thing
davidfor is offline   Reply With Quote