How to clear cache?

[odamizu]

Hi there,

I've been experiencing this problem where, in the course of reading, page rendering will flake out and the bottom half of the page will be missing. Going a page forward then back will restore the full text. More details here.

Using ;dm I think I've pointed the problem to the following error:

framework: [41m[PRE_RENDER] fillUpCache(533): ERROR: NO page cache list or current page is a special page that shouldn't use cache[0m

Is there a way to clear the cache short of restarting the Kindle? (which does seem to help temporarily, but is annoying to do in the middle of reading).

Also, if there are any ideas what "No page cache list" means, I'd appreciate it. (There's nothing special about the page, it's just straight text, no different formatting or illustrations or unusual page elements, so the second half of the error message seems not to apply.)

This problem started for me with 5.8.5.0.2 and persists through 5.8.8, though I've heard people have experienced it prior to 5.8.5.0.2. It happens on both Oasis and Voyage and with every book.

Thanks for any ideas!

[knc1]

What is special about the page?

It is "Framework" that is complaining, would just restarting "Framework" be a quicker fix than a full restart?

There is a way to restart "Framework", MrPI uses it.
I don't think I ever knew how to do it, isn't there a button for that on the KUAL menu?

[odamizu]

There's nothing special about the page. It's just plain straight text, no special formatting, no images, no tables, no nuthin'. That's what's so frustrating about this bug. (And it's possible this error message has nothing to do with the bug, since it will occur a few times before the bug occurs. The only reason I think it's related is because this is the error message that occurs immediately before the bug.)

As for Framework, I don't know what that means! Nor do I know how to restart Framework, who MrPI is or how to use KUAL (though I suspect that requires jailbreaking, which is beyond my courage level).

<sigh> Would going back to the Home page or putting my Kindle to sleep and waking it back up affect the cache? It doesn't seem to help with the bug, so if going Home or going to sleep clears the cache, then maybe the cache isn't the issue.

Thanks for any help!

[knc1]

Originally Posted by odamizu

There's nothing special about the page. It's just plain straight text, no special formatting, no images, no tables, no nuthin'. That's what's so frustrating about this bug. (And it's possible this error message has nothing to do with the bug, since it will occur a few times before the bug occurs. The only reason I think it's related is because this is the error message that occurs immediately before the bug.)

As for Framework, I don't know what that means! Nor do I know how to restart Framework, who MrPI is or how to use KUAL (though I suspect that requires jailbreaking, which is beyond my courage level).

<sigh> Would going back to the Home page or putting my Kindle to sleep and waking it back up affect the cache? It doesn't seem to help with the bug, so if going Home or going to sleep clears the cache, then maybe the cache isn't the issue.

Thanks for any help!

Yes, those things are part and parcel of what is included in the jailbreak packages.
I just thought everyone here has a jailbroken device.
But I now remember we are only over here to keep HarryT happy.
I guess he has extended his rules to cover "no undocumented feature discussions" in the main forum.

There are a lot of "cache" things used in the system, all mostly to speed the wake-up from sleeping.
So just letting it go to sleep and waking it up again will probably not clear the problem.

The multiple messages before anything happens visually could be part of the problem. It is just not easy to say.

I'll try reading NiLuJe's work, and see if the "framework" restart can be done without a jailbreak. Most likely not.

Linux (like all *nix flavors) is concurrent multi-user by design, un-like some O.S. brands that charge you extra for each (concurrent) user you want to use.

"Framework" is the name of one of the (internal) system users.
The name is also suggestive of its function in the overall plan of things.

"cvm" is the name of the user who runs the Java virtual machine (a Commercial Virtual Machine - not the freebe JVM Sun/Oracle lets people download).

"root" is the name of the administrator - this one for historical reasons, not because it is the name of a computer character on PoI. On PoI, the administrator of the 'good' computer system is "admin" and the administrator of the 'bad' computer system is 'root'. I have never seen any reports on how much MS paid to have those things included in the script.

There are others, but those are the ones you will see mentioned here most often.

[odamizu]

Thank you, knc1, for all your info.

Originally Posted by knc1

I'll try reading NiLuJe's work, and see if the "framework" restart can be done without a jailbreak. Most likely not.

Can I assume that Restarting my Kindle will also restart "framework" and clear the cache?

[knc1]

Originally Posted by odamizu

Thank you, knc1, for all your info.



Can I assume that Restarting my Kindle will also restart "framework" and clear the cache?

Yes.
But there should be a more elegant way, if I can find it.

[odamizu]

Cool! Thanks!

[NullNix]

Originally Posted by knc1

"cvm" is the name of the user who runs the Java virtual machine (a Commercial Virtual Machine - not the freebe JVM Sun/Oracle lets people download).

That's not what it ever stood for. It originally stood for Compact Virtual Machine, but then it was decided that this would be confusing due to the acronym's similarity with KVM (?!) so it was decreed that the C stood for, uh, itself: the letter C. Because calling a Java virtual machine "C Virtual Machine" is not confusing at all!

Combine this with the SunOS/Solaris version disaster and you must conclude that Sun had a genius for terrible renaming decisions.

[knc1]

Originally Posted by NullNix

That's not what it ever stood for. It originally stood for Compact Virtual Machine, but then it was decided that this would be confusing due to the acronym's similarity with KVM (?!) so it was decreed that the C stood for, uh, itself: the letter C. Because calling a Java virtual machine "C Virtual Machine" is not confusing at all!

Combine this with the SunOS/Solaris version disaster and you must conclude that Sun had a genius for terrible renaming decisions.

It is the terminology currently used by Oracle for the proprietary, hardware assisted, VM.

But as you point out, that might be an accident;
after all there are only 26 letters to choose from.