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!

Fungovanie tejto stránky je z dôvodu údržby dočasne obmedzené. Ak článok nevyrieši váš problém a chcete položiť otázku, napíšte našej komunite podpory na Twitter @FirefoxSupport alebo Reddit /r/firefox.

Vyhľadajte odpoveď

Vyhnite sa podvodom s podporou. Nikdy vás nebudeme žiadať, aby ste zavolali alebo poslali SMS na telefónne číslo alebo zdieľali osobné informácie. Nahláste prosím podozrivú aktivitu použitím voľby “Nahlásiť zneužitie”.

Ďalšie informácie

History not recording all websites, gaps in history

  • 1 odpoveď
  • 1 má tento problém
  • 1 zobrazenie
  • Posledná odpoveď od cor-el

more options

(First off; I have not changed any settings related to history in firefox, nor is firefox configured to delete history, nor am I in private mode) For all purposes, all the history is set to be remembered and saved. (I am also the sole user of this computer)

Started having this problem this last weekend (Around June the 6th 2020) At first I didn't notice but after a while large portions (hours worth) of my history were missing. The problem seems may have gotten worse , more and more seems to vanish. To be specific seemingly randomized pages fail to register in the history.

I have attempted verifying the integrity of places.sqlite (is this even history?) as was mentioned on another similar support report (about history not recording everything) but as soon as I pressed verify the log showed the following -

> Task: checkIntegrity - Unable to check places.sqlite integrity: Error: Error(s) encountered during statement execution: > 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.

Can I repair my current places.sqlite (Bookmarks / History?) ? Do I have to delete it/other places.sqlite files so firefox can regenerate?

I have a lot of bookmarks, is there such a thing as too many?

(First off; I have not changed any settings related to history in firefox, nor is firefox configured to delete history, nor am I in private mode) For all purposes, all the history is set to be remembered and saved. (I am also the sole user of this computer) Started having this problem this last weekend (Around June the 6th 2020) At first I didn't notice but after a while large portions (hours worth) of my history were missing. The problem seems may have gotten worse , more and more seems to vanish. To be specific seemingly randomized pages fail to register in the history. I have attempted verifying the integrity of places.sqlite (is this even history?) ''as was mentioned on another similar support report (about history not recording everything)'' but as soon as I pressed verify the log showed the following - > Task: checkIntegrity - Unable to check places.sqlite integrity: Error: Error(s) encountered during statement execution: > 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. Can I repair my current places.sqlite (Bookmarks / History?) ? Do I have to delete it/other places.sqlite files so firefox can regenerate? I have a lot of bookmarks, is there such a thing as too many?

Vybrané riešenie

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

You can check for problems with the places.sqlite and favicons.sqlite files in the Firefox profile folder.

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

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

If "Verify Integrity" cannot repair places.sqlite, rename/remove all places.sqlite and favicons.sqlite files in the Firefox profile folder. Firefox will rebuild places.sqlite and restore the bookmarks from a 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

See also:

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

See also:

Čítať túto odpoveď v kontexte 👍 0

Všetky odpovede (1)

more options

Vybrané riešenie

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

You can check for problems with the places.sqlite and favicons.sqlite files in the Firefox profile folder.

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

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

If "Verify Integrity" cannot repair places.sqlite, rename/remove all places.sqlite and favicons.sqlite files in the Firefox profile folder. Firefox will rebuild places.sqlite and restore the bookmarks from a 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

See also:

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

See also: