Go to about:support, scroll down to the "Places Database" heading, click the "Verify Integrity" button and see what the output says.

Go to about:support, scroll down to the "Places Database" heading, click the "Verify Integrity" button and see what the output says.

> Task: checkIntegrity - Unable to fix corruption, places.sqlite will be replaced on next startup > Task: invalidateCaches - The task queue was cleared by an error in another task. > Task: checkCoherence - The task queue was cleared by an error in another task. > Task: expire - The task queue was cleared by an error in another task. > Task: originFrecencyStats - The task queue was cleared by an error in another task. > Task: vacuum - The task queue was cleared by an error in another task. > Task: stats - The task queue was cleared by an error in another task. > Task: _refreshUI - The task queue was cleared by an error in another task.

It's not realistic to continue to use a corrupted database. You should be able to keep your bookmarks in the new rebuilt database, only the history is lost. If you really need that history, you could try various database recovery tools.

It's not realistic to continue to use a corrupted database. You should be able to keep your bookmarks in the new rebuilt database, only the history is lost. If you really need that history, you could try various database recovery tools.

I have been using the "corrupt" file for over two years now and it has history since 2014 and I don't want to lose it. Can you suggest any database recovery tool? I took your advice and tried DB Browser for SQLite, but the Integrity Check showed no errors. Any other tool that can help?

You could try using an extension like History Export to transfer history from the corrupted database into the good one.

You could try using an extension like History Export to transfer history from the corrupted database into the good one.

Thank you but it didn't work. It exports the history to a file, but when importing, nothing happens. History doesn't come back. And of course, everytime I restart Firefox, I have to rename the old corrupt file again and again. I tried to repair the SQLite file with SQLite Expert, but Firefox wouldn't read it and always created a new file even after renaming the old corrupt file. What I don't understand is if the file is corrupt, why does it work after renaming.

When you rename the file, Firefox doesn't know it is corrupt until the next time its integrity is checked.

History Export version 0.4 released a few hours ago works for me.

When you rename the file, Firefox doesn't know it is corrupt until the next time its integrity is checked. History Export version 0.4 released a few hours ago works for me.

Thank you, it finally worked and solved the issue. The new places file is 90mbs, 15 mb smaller than the last one, but that's okay. Thank you for your help.