New Test Version Posted
2021-07-14
- Change blockfilecache to save uint32 addrs instead of original cache key. Hashing cache key proved unreliable in some cases.
- Allow fictionpress.com with use_browser_cache--user still needs to configure in personal.ini Closes #716
Quote:
Originally Posted by steltek
I've included the contents of the cache folders for Chrome and Edge in separate WinRAR files attached. I've also attached the job log showing the chapter 69 error as a text file.
...
|
Okay, once I could see it happen in front of me, I was able to track this down better.
The Chrome Block Cache code was basically hashing the cache key to a binary address via a hash table, but in that particular case, the hash pointed to a null (0s) address in the table.
But during the initial cache table scan (to find the ffnet URLs), the binary address was already known.
So I changed the code to save and use the binary address and skip the hashing/lookup step altogether.
It's now working for me on the examples given and should even give a (minor) performance boost.
Note that this change
only affects Chrome derived browsers using Block Cache. Many Chrome browsers use Simple Cache instead--I've no idea which or why.
Quote:
Originally Posted by Nutzer0815
...
Directory does not contain a known browser cache type: 'C:\Program Files\Calibre2'
...
|
This error indicates that your
browser_cache_path isn't set correctly, since it's trying to use 'C:\Program Files\Calibre2'.
Perhaps you have
browser_cache_path appearing more than once?