Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

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

Deleted places sqlite, now firefox wont start

  • 3 பதிலளிப்புகள்
  • 1 இந்த பிரச்சனை உள்ளது
  • 4 views
  • Last reply by Glamdring7

I noticed the bookmarks were all messed up, first I tried to restore them and the cpu went to 100% for over 10 minutes and not responding. Then I found an article that said to delete places.sqlite and restart. Now the same thing, cpu has been at 100% for over 15 minutes and is no longer responding. The main screen does not come up at all now.

I copied the old places file back in, it starts, but the still can restore the bookmarks.

I noticed the bookmarks were all messed up, first I tried to restore them and the cpu went to 100% for over 10 minutes and not responding. Then I found an article that said to delete places.sqlite and restart. Now the same thing, cpu has been at 100% for over 15 minutes and is no longer responding. The main screen does not come up at all now. I copied the old places file back in, it starts, but the still can restore the bookmarks.

All Replies (3)

Hold down the Shift key (On Mac the Options key) while starting Firefox to start in Safe Mode. See if the problem is still there.

FF does start like that, but now all the bookmarks are gone. The places.sqlite file is now 10.5M, before it was almost 50M, but that too is gone.

I tried to manually import one of the old json files in a new profile, but spiked the CPU again. Guessing the json is corrupt and will have to find an old html backup.