28.17.0 - New/fresh profiles cache issue
Posted: 2020-12-22, 15:15
The cache doesn't seem to be indexed properly after each session.
I'm not sure how to call it properly, but basicaly if you visited a website or two, to get cache going, and then restarted Pale Moon and look in about:cache the size of the disk cache will be precisely... 0
(assuming the home page is set to about:home).
The cache2 folder is missing 2 index files (index & index.log) on fresh profiles. Also after each session the cache.trash* folders seems to be piling up (precisely 12 MB in size, each of them).
This problem seems to affect fresh profiles, and existing profile copies. Basicaly any profile that don't have corresponding cache folder in appdata/local/... created in the past.
As for how much in the past? One of my test profiles was definately created pre 28.17 (28.16 or 28.15 I think) has the exact problem.
Copying entire cache folder (randomstring.profilename in appdata/local/...) of an older profile (without this issiue) in to a affected one... kind of works.
At least about:cache doesn't show 0 after each session, even after clearing the cache through the browser UI.
But the index files (in cache2 folder) (at least if I remember correctly) stay the exact same size as before the cache clear (although this might be some quirk in windows explorer, or perhaps I'm starting to loose my mind...).
Shouldn't the index file(s) get deleted after the clear?
I'm not sure if it is something just on my end, but if it's not, then it should be easily reproduciable.
I'm not sure how to call it properly, but basicaly if you visited a website or two, to get cache going, and then restarted Pale Moon and look in about:cache the size of the disk cache will be precisely... 0
(assuming the home page is set to about:home).
The cache2 folder is missing 2 index files (index & index.log) on fresh profiles. Also after each session the cache.trash* folders seems to be piling up (precisely 12 MB in size, each of them).
This problem seems to affect fresh profiles, and existing profile copies. Basicaly any profile that don't have corresponding cache folder in appdata/local/... created in the past.
As for how much in the past? One of my test profiles was definately created pre 28.17 (28.16 or 28.15 I think) has the exact problem.
Copying entire cache folder (randomstring.profilename in appdata/local/...) of an older profile (without this issiue) in to a affected one... kind of works.
At least about:cache doesn't show 0 after each session, even after clearing the cache through the browser UI.
But the index files (in cache2 folder) (at least if I remember correctly) stay the exact same size as before the cache clear (although this might be some quirk in windows explorer, or perhaps I'm starting to loose my mind...).
Shouldn't the index file(s) get deleted after the clear?
I'm not sure if it is something just on my end, but if it's not, then it should be easily reproduciable.