Quote:
Originally Posted by knc1
1 = yes
2 = yes
3 = yes (rebuilds new font cache, then renders current page, in-validates other cached pages)
4 = only if it causes a '3'
5 = no (because if you go back to book, you go to the last page opened)
6 = no (because there is no 'reset' or 'restart' involved, only suspend (freeze everything) and resume (unfreeze every thing).
Since the reader is closed source, the above is only what can be reasonably expected.
But that does not mean the programmer who wrote it was doing what is reasonably expected.
|
I see no evidence that anything is wrong with the font cache, which is persistent, built by fontconfig and contains expensive-to-compute font metric and family data for matching. This appears to be some *other* cache, probably a cache of uncompressed/prerendered MOBI/AZW3 stuff (i.e. pre-run through the HTML renderer). It is probably not the cache that runs ahead a few pages and computes the precise pixel transitions needed to get from one purely-textual page to another one without blinking through black, since I've had this problem on transitions both to and from pages with images on, where that cache is apparently disabled. Both this mysterious "other" cache and the pixel-transition cache are almost certainly purely in-memory things and only last for a few page turns at most -- but whatever it is that makes the cache management go so wrong *might* be resolved by one of those means. I don't know. This is all guesswork on my part
Kindles have a lot of caches.