Quote:
Originally Posted by odamizu
I think we're looking at a caching problem.
This is the error that immediately precedes the missing-text bug:
Code:
framework: [41m[PRE_RENDER] fillUpCache(533): ERROR: NO page cache list or current page is a special page that shouldn't use cache[0m
However, the bug doesn't happen every time the error occurs, and once it starts happening, it recurs with shorter intervals in between.
Over the course of 30 minutes of reading: - error occured 9 times before missing-text bug occurred
- then 3 times followed by missing-text bug
- then 2 times followed by missing-text bug
There's nothing special about the pages where the bug occurs — no illustrations or graphics or tables or anything else unsual. It's just plain old straight text. So I don't think the problem is "a special page that shouldn't use cache."
Therefore, it seems the problem is "No page cache list", though I don't understand what that means. Any ideas?
Another thought that occurred to me is that I need really big font size (resulting in 12 lines per screen with medium line-height). As a result, each screen doesn't have a lot of words, and each book has many more "screen-pages" than a person reading with a more normal font-size. I'm also probably turning pages faster than the average reader because I have fewer words per page.
Do other people experiencing this bug also use large font-sizes?
If this is indeed the problem, and changing font-size is not an option for me, any suggestions on how to ease pressure on the cache?
(This is particularly frustrating because this bug never occurred prior to 5.8.5.0.2 and it has persisted through 5.8.8.)
Thanks for any thoughts! |
Sorry...I don't think it's large font size-related. There are many times that I have to use font sizes that large when my eyes are tired, and I've never seen the bug.
Shari