Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

Cleaning Cache History makes CPU hang for hours.

  • 1 reply
  • 3 have this problem
  • 6 views
  • Last reply by cor-el

kangarooo
kangarooo
more options

My FF settings history remembering is 90 days.

Each day having approximatly 1000 pages.


Today FF started to hang even when just writing thats why i wanted to solve problem with solthing witch has a problem- CLEAN CACHE AND HISTORY.

1. Closed FF

2. Opened FF

3. Clicked to clean all HISTORY EVERYTHING

P.roblem- it started to use all CPU and every 25 second it pops up UNRESPONSINVE SCRIPT.

I click continue couse that of course is not for websites (couse none is opened now) but for history cleaning FF script.

Unless i click continue it doesnt work with cleaning history right? Or not?- all cpu is down, so no cleaning happening, but i want to clean history.

My FF settings history remembering is 90 days. Each day having approximatly 1000 pages. Today FF started to hang even when just writing thats why i wanted to solve problem with solthing witch has a problem- CLEAN CACHE AND HISTORY. 1. Closed FF 2. Opened FF 3. Clicked to clean all HISTORY EVERYTHING P.roblem- it started to use all CPU and every 25 second it pops up UNRESPONSINVE SCRIPT. I click continue couse that of course is not for websites (couse none is opened now) but for history cleaning FF script. Unless i click continue it doesnt work with cleaning history right? Or not?- all cpu is down, so no cleaning happening, but i want to clean history.

Modified by kangarooo

All Replies (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

Current Firefox versions keep a maximum number of visited page and do not have a time limit for the history. Firefox determines automatically how many pages can be kept without affecting the performance. You can see the current value of this maximum as the value of the read-only pref places.history.expiration.transient_current_max_pages on the about:config page. See Marco Bonardo's blog about this subject:

If you still have browser.history_expire_days prefs then you can reset them via the right-click context menu.

You can delete all places.sqlite files including places.sqlite-shm and places.sqlite-wal in case there is a problem with the file.

You can check for problems with the places.sqlite database file in the Firefox profile folder.