This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Firefox 105 update corrupts places.sqlite

  • 3 balasan
  • 0 ada masalah ini
  • 4 paparan
  • Balasan terakhir oleh tikkoneus

more options

Auto-updated to v105 today (105.0.2 64-bit Windows 10) and all bookmarks were gone. Not just gone but the bookmark manager seems not to be rendering properly (see attached image where there should be at least some elements drawn). Additionally, neither the bookmarks nor history left pane show anything (second attachment).

The 105 update was applied this morning when first opening the browser. Profile folder -> bookmarkbackups shows a backup from just before the update. Bookmark library -> Restore gives that backup as an option, but restoring that backup has no effect (does nothing).

Exiting Firefox and manually moving places.sqlite to a backup location and then restarting also has no effect. places.sqlite is rebuilt but library -> restore still has no effect.

Auto-updated to v105 today (105.0.2 64-bit Windows 10) and all bookmarks were gone. Not just gone but the bookmark manager seems not to be rendering properly (see attached image where there should be at least some elements drawn). Additionally, neither the bookmarks nor history left pane show anything (second attachment). The 105 update was applied this morning when first opening the browser. Profile folder -> bookmarkbackups shows a backup from just before the update. Bookmark library -> Restore gives that backup as an option, but restoring that backup has no effect (does nothing). Exiting Firefox and manually moving places.sqlite to a backup location and then restarting also has no effect. places.sqlite is rebuilt but library -> restore still has no effect.
Lampirkan skrinsyot

All Replies (3)

more options

Possibly related to https://bugzilla.mozilla.org/show_bug.cgi?id=1792171, though not on mobile?

more options

If you use Sync then best is to disconnect Sync temporarily during troubleshooting.

this could be a problem with the places.sqlite and favicons.sqlite files in the Firefox profile folder.

  • use the "Places Database" -> "Verify Integrity" button on the "Help -> More Troubleshooting Information" (about:support) page

If errors are reported with "Verify Integrity", close and restart Firefox or reboot and retry.

If "Verify Integrity" cannot repair places.sqlite, rename/remove all places.sqlite and favicons.sqlite files in the Firefox profile folder with Firefox closed. Firefox will rebuild places.sqlite and restore the bookmarks from the most recent JSON backup in the bookmarkbackups folder.

  • keep a backup copy of places.sqlite in case a new places.sqlite database has to be created
  • you lose the history when a new places.sqlite is created

You may have to restore an older bookmarks backup in the bookmarkbackups folder via the Bookmarks Manager (Library).

See also:

You can use the button on the "Help -> More Troubleshooting Information" (about:support) page to go to the current Firefox profile folder or use the about:profiles page (Root directory).

more options

I'm not sure what happened. Last week with 105.0.2 it showed nothing in the side bars. Yesterday the bookmarks side bar still showed nothing but the history side bar showed an xml error I didn't write down, something about "error on line 1 character 1: no content".

Today I'm upgraded to 105.0.3 which appears not to have anything to do with history or places (see changeset here: https://hg.mozilla.org/releases/mozilla-release/rev/5a2af3ed86a64618b34bde6f427f2132b13f6bed)

But the bookmarks and history are back!

Perhaps there's an obscure race condition where the side bars can be created and populated before they have access to the data from places.sqlite? I don't know how those are plumbed together but this feels like non-deterministic behavior.