FF 79 have new storage-sync-v2.sqlite, storage-sync-v2.sqlite-shm, storage-sync-v2.sqlite-wal files in profile folder. When I exit Firefox, storage-sync-v2.sqlite-shm, storage-sync-v2.sqlite-wal files are kept and not deleted unlike cookies.sqlite-wal, cookies.sqlite-shm, favicons.sqlite-shm, favicons.sqlite-wal. By the way, CCleaner > Custom Clean > Applications > Firefox > "Internet Cache" option deletes all *.sqlite-shm, *.sqlite-wal, so CCleaner deletes these two files too. storage-sync-v2.sqlite-wal store addon settings that uses the sync API, so I lose the addon settings changed that is not yet applyed to storage-sync-v2.sqlite. So, please don't delete *.sqlite-shm, *.sqlite-wal with that option. CCleaner > Custom Clean > Applications > Firefox > "Compact Databases" option deletes all *.sqlite-shm, *.sqlite-wal too(so, CCleaner don't have to deletes it in "Internet Cache" option), but apply these to *.sqlite files before delete it, so I don't lose my data.
It's a beta though, and I personally wouldn't have any cleaning tool (not just CCleaner) cleaning a beta version of a web browser.
Piriform have enough on their plate to keep up with Stable builds of web browsers. With beta/nightly builds of browsers they logically can't chase those and keep up because they'd likely have to release a new CCleaner version daily or weekly.
<div class="ipsQuote_contents">
<p>
It's a beta though, and I personally wouldn't have any cleaning tool (not just CCleaner) cleaning a beta version of a web browser.
</p>
<p>
Piriform have enough on their plate to keep up with Stable builds of web browsers. With beta/nightly builds of browsers they logically can't chase those and keep up because they'd likely have to release a new CCleaner version daily or weekly.
</p>
</div>
It's not beta problem. "Internet Cache" option deletes all *.sqlite-shm, *.sqlite-wal without apply these to *.sqlite files before delete it. so, if firefox is not shutting down properly and these files are remains, CCleaner will delete it and users will lose data. As I said, "Compact Databases" option deletes all *.sqlite-shm, *.sqlite-wal too, but apply these to *.sqlite files before delete it. so, CCleaner don't have to deletes it in "Internet Cache" option.
With it being a beta I wouldn't get any hopes of them doing anything with it, the user base of a non-stable beta would be lower compared to a stable release that will auto-update via the browser itself. Even with stable builds there's a delay and things don't get an immediate fix, and by the time they release a new version something else can change in browsers hence they're always playing catch up.
I have just installed Firefox 79.0 (release version) and can confirm the problem.
If an extension makes changes to the new "storage-sync-v2.sqlite", the files ".sqlite-shm" and ".sqlite-wal" are not inserted into the "storage-sync-v2.sqlite" when Firefox is closed. If they are deleted by the CCleaner rule "Internet Cache", all changes will be lost.
You should therefore remove the deletion of the ".sqlite-shm" and ".sqlite-wal" files from the rule "Internet Cache". It is also not necessary that these files are deleted by the rule "Internet Cache", because there is still the rule "Compact Databases".
The rule "Compact Databases" does everything right, because it merges the ".sqlite-shm" and ".sqlite-wal" files with the ".sqlite" file and compresses it afterwards.
I personally exclude all ".sqlite-shm" and ".sqlite-wal" files in the Firefox profile since a long time, because it happened from time to time that Firefox databases were not closed correctly when exiting.
Drive or Folder: %AppData%\Mozilla\Firefox\Profiles\*\
File Types:.sqlite-shm;.sqlite-wal
(In this special case it would of course be sufficient to exclude only the files for the "storage-sync-v2.sqlite".)
Thanks for showing your line, I just wanted to make sure my wildcards were correct.
I'm aware you can do that from within CCleaner, but CCleaner dosn't do wildcards, it'll show the complete path instead of shortened "%AppData%" for example, yours, and now mine is much cleaner, simpler and even a little more private.
Okay, I understand. ? Right, thanks to the environment variable and the wildcard the entry is even valid for all existing Windows users and Firefox profiles.
For those who don't have a ccleaner.ini, or don't want to edit it manually, you can apply the exclusion/workaround like this:
After using Firefox close it again.
Open ccleaner and go to Custom Clean.
Click on Analyze
Double click on 'Firefox - Internet Cache' (You may need to expand the window to see the full pathnames, but they may be the only two files there).
Right click on '...\storage-sync-v2.sqlite-wal'
Click on 'Add to Exclude list'
Right click on '...\storage-sync-v2.sqlite-shm'
Click on 'Add to Exclude list'
Job done.
Note also that Exclusions only apply to Custom Clean, Health Check ignores Exclusions.
PS. If you don't have your Firefox synced with a Firefox account then you don't need this workaround.
<div class="ipsQuote_contents">
<p>
...PS. If you don't have your Firefox synced with a Firefox account then you don't need this workaround.
</p>
</div>
Just an FYI that multiple users who <strong>do not use Firefox Sync</strong> have reported that CCleaner v5.69 wiped the custom settings of NoScript and other Firefox extensions in the Norton Tech Outpost thread <em><a href="https://community.norton.com/en/comment/8450581#comment-8450581" rel="external nofollow">Firefox 79.0 to be Released July 28</a></em>.
I use Firefox ESR v68.11.0 (the extended support release of Firefox) so I haven't been affected by this CCleaner bug, but I've disabled all Firefox cleaning in my CCleaner settings and will only use Firefox's built-in browser history cleaning (Tools | Options | Privacy & Security | History |Clear history when Firefox closes | Settings) until a bug fix is released. It's unfortunate that someone from Avast/Piriform didn't investigate sooner when the OP circcc first reported this issue back on 01-Jul-2020 with an early beta release of FF 79. Kudos to them for at least trying to get someone's attention.
I solved the Firefox 79 issue and the issue with NoScript! I just now uninstalled CCleaner (paid version). Ta-Da problem gone! Although there are workarounds posted in the messages above, why should I have to patch CCleaner for it's core functionality--- working seamlessly with a web browser.
I will check back occasionally. Hopefully one of you will post up when the problem is fixed.
<div class="ipsQuote_contents ipsClearfix" data-gramm="false">
<p>
why should I have to patch CCleaner for it's core functionality--- working seamlessly with a web browser.
</p>
</div>
Partly tounge-in-cheek, but:
Remember that it is the browser that changed things, not CCleaner which now has to catch up with what the browser programmers changed (as will all other 3rd party cleaners).
So shouldn't you really be shouting at mozilla for changing things in the first place?
<div class="ipsQuote_contents ipsClearfix" data-gramm="false">
<p>
</p>
<p>
So shouldn't you really be shouting at mozilla for changing things in the first place?
</p>
</div>
On the other hand it is up to CCleaner devs to check these things.