Thanks for sharing the DB file!
I suspect that the file is this big because of old entries marked for deletion, perhaps due to invalid purging. When I run `VACUUM` on it the file size reduces to ~ 100kb. With the bug in Fx112 Firefox may have purged cookies wrongly for you.
While 112.0.1 doesn't fix the invalid timestamps itself we don't expect it to do any additional invalid purging. To confirm, if you use a DB that has never been loaded in Fx112 (but an older version) and you directly upgrade to Fx112.0.1, do you still loose cookies in the process?
> but apparently the new version just removed some older fix
The patch that has been backed out for Fx112.0.1 is (/was meant to be) a test only change, so we're not removing a fix. This will also not fix up an already purged / corrupted DB.
Bug 1827988 Comment 22 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Thanks for sharing the DB file!
I suspect that the file is this big because of old entries marked for deletion, perhaps due to invalid purging. When I run `VACUUM` on it the file size reduces to ~ 100kb. With the bug in Fx112 Firefox may have purged cookies wrongly for you.
While 112.0.1 doesn't fix the invalid timestamps itself we don't expect it to do any additional invalid purging. To confirm, if you use a DB that has never been loaded in Fx112 (but an older version) and you directly upgrade to Fx112.0.1, do you still loose cookies in the process?
> but apparently the new version just removed some older fix
The patch that has been backed out for Fx112.0.1 is (/was meant to be) a test only change, so we're not removing a fix. This will also not fix up an already purged / corrupted DB.