Showing questions tagged: Show all questions

Firefox keeps turning "cookies.sqlite" into .bak since it updated to version 74.0

Immediately after updating to version 74.0, I noticed Firefox had logged me out from all sites I usually am automatically logged into at the start of a session. It was n… (read more)

Immediately after updating to version 74.0, I noticed Firefox had logged me out from all sites I usually am automatically logged into at the start of a session. It was not the first time I encountered this problem, as it had been happening at irregular intervals, and found that it was caused by firefox replacing the "cookies.sqlite" file in my profile folder with a new one, while also dubbing the old one "cookies.sqlite.bak". I always resolved the problem by:

-Closing Firefox

-Deleting the recently created "cookies.sqlite" in my profile folder

-Renaming "cookies.sqlite.bak" into "cookies.sqlite"

-(Usually) Creating a copy of the .bak file and keeping it in a folder as insurance, in case I found no recent .bak the next time it happened or it got corrupted somehow

After doing this, upon starting firefox I would find all my cookies in place and myself logged in all sites I cared about (I set it up so that firefox restores a long-running, multi-windowed session at startup).

On a side note, I was always able to know whether my "cookies.sqlite" file had been rewritten by checking its size: if it had been just created, it would always be 512 Kb; the backup .bak file is instead 1.50 Mb.


Onto the problem at hand: after updating to 74.0 and finding that I lost all cookies and logins, I repeated the process highlighted above, as usual. It didn't resolve the problem though: I still didn't recover any cookie even though I switched the "good" .bak file with the newly created "cookies.sqlite". Upon starting firefox, instead of loading my 1.50 Mb .sqlite it keeps immediately renaming it .bak and creating its own cookies.sqlite. I even tried using a slightly older .bak, one that I had successfully switched before: the result was the same.

I am at my wits' end: I checked and tried various cookie and privacy settings, but since firefox updated it seems determined to shun my old cookie backup in favor of creating its own empty, useless file. There also doesn't seem to be any recent documentation on this problem I can find. I even considered opening and checking both .sqlite and .bak files for any obvious differences, but I'm afraid I just don't know how.


Those cookies are critical for my navigation. "Major Annoyance" wouldn't even begin to describe starting a session without those.

Asked by chibi95 4 months ago

Last reply by jscher2000 4 months ago

  • Archived

Firefox now holds a lock for places.db during the whole time it is open

Since the last couple of days, I see that Firefox holds a lock for places.db for the whole time while Firefox is open. The problem manifests itself when I use alfred work… (read more)

Since the last couple of days, I see that Firefox holds a lock for places.db for the whole time while Firefox is open. The problem manifests itself when I use alfred workflow to do a search for a firefox bookmark by a keyword. I see that the workflow written in Python crashes with

`sqlite3.OperationalError: database is locked`

When I close Firefox, the script is working fine. When I open it again - the script is not operational again. Tried safe mode - the same result.

This was working fine for years and the symptom points that it was changed recently and now Firefox holds a lock during the whole time it is open. I guess previously the database lock was acquired per bookmark write transaction.

FF 63.0 macOS

Is it a known issue? Why was this change made?

Thanks!

Asked by dmfigol 1 year ago

Last reply by Roland Tanglao 1 year ago