Søg i 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.

Læs mere

Firefox using large amount of cache, starts running slow and will crash when closing.

  • 5 svar
  • 1 har dette problem
  • 6 visninger
  • Seneste svar af Jer

more options

Firefox using large amount of cache, starts running slow and will crash when closing. This started a couple months ago and I haven't made any changes other than FF updates and MS updates. To fix this I just run CCleaner and start FF back up, then all runs fine for a day or so. Sometimes I go into Tools, Settings, Privacy & Security, Cookies and Site Data and clear Cache (not cookies). It is normal to see cache at around 511 MB of cache. It starts out fresh at 55.1 MB. I start FF with 8 tabs open. FF is the only application that I start. I didn't use to have this problem, not sure when exactly started. I do have Performance at "Use recommended performance settings". No "hardware acceleration" is checked. Now I do recall some time ago I did not check Use "recommended performance settings" and I checked the number of threads or something like that would be used, I forget exact terminology, but that option seems to have gone away with one of the FF updates

Running FF 94.0.2 (Yes I know 95 is out) Dell Optiplex 8GB Intel Core i5 Windows 10 Pro 21H2 19044.1387

No new addon using Flagfox, Tab Reloader, NoScripts, Undo Close Tab, Webroot Threat Shield and Facebook Container. These have been used for years with no issues.

FF Task manager shows most things low, the highest memory usage Gmail at 27MB.

Right now when using Microsoft Task Manager (I just started FF) I find it using 15 processors for 752MB. Sometimes I have seen up to 40 FF processors. Most are not using any CPU or other resources. Microsoft Task Manager shows 6% CPU, 47% Memory, 2% Disk, 0% Network, 5%GPU. Not at all busy, but running okay now, will take awhile to start the running slow.

Now after all that, is there anything I should be checking or changing? Just went up to 23 FF processors running via viewing MS Task Manager. Still no load on resources.

Firefox using large amount of cache, starts running slow and will crash when closing. This started a couple months ago and I haven't made any changes other than FF updates and MS updates. To fix this I just run CCleaner and start FF back up, then all runs fine for a day or so. Sometimes I go into Tools, Settings, Privacy & Security, Cookies and Site Data and clear Cache (not cookies). It is normal to see cache at around 511 MB of cache. It starts out fresh at 55.1 MB. I start FF with 8 tabs open. FF is the only application that I start. I didn't use to have this problem, not sure when exactly started. I do have Performance at "Use recommended performance settings". No "hardware acceleration" is checked. Now I do recall some time ago I did not check Use "recommended performance settings" and I checked the number of threads or something like that would be used, I forget exact terminology, but that option seems to have gone away with one of the FF updates Running FF 94.0.2 (Yes I know 95 is out) Dell Optiplex 8GB Intel Core i5 Windows 10 Pro 21H2 19044.1387 No new addon using Flagfox, Tab Reloader, NoScripts, Undo Close Tab, Webroot Threat Shield and Facebook Container. These have been used for years with no issues. FF Task manager shows most things low, the highest memory usage Gmail at 27MB. Right now when using Microsoft Task Manager (I just started FF) I find it using 15 processors for 752MB. Sometimes I have seen up to 40 FF processors. Most are not using any CPU or other resources. Microsoft Task Manager shows 6% CPU, 47% Memory, 2% Disk, 0% Network, 5%GPU. Not at all busy, but running okay now, will take awhile to start the running slow. Now after all that, is there anything I should be checking or changing? Just went up to 23 FF processors running via viewing MS Task Manager. Still no load on resources.

Ændret af Jer den

Alle svar (5)

more options

More than one process is normal for the current Firefox. http://www.ghacks.net/2016/07/22/multi-process-firefox/

Multi-process Firefox is codenamed "e10s". https://wiki.mozilla.org/Firefox/multiprocess


In the address bar, type about:crashes<enter>. Note: If any reports do not have BP- in front of the numbers/letters, click it to submit them.

The crash report is several pages of data. We need the report numbers to see the whole report.

Using your mouse, mark the most recent 7 - 10 Submitted crash reports, and copy them. Now go to the reply box and paste them in.

Please, Do not post a screenshot ! !

aboutcrashesFx57

For more help on crash reports, see; https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support

more options

Start Firefox using Troubleshoot(Safe) Mode {web link}

A small dialog should appear. Click Start In Troubleshoot(Safe) Mode (not Refresh). Is the problem still there?


https://support.mozilla.org/en-US/kb/firefox-slow-how-make-it-faster

https://support.mozilla.org/en-US/kb/firefox-uses-too-many-cpu-resources-how-fix

https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-ram

https://support.mozilla.org/en-US/kb/firefox-hangs-or-not-responding

https://support.mozilla.org/en-US/kb/firefox-takes-long-time-start-up

https://support.mozilla.org/en-US/kb/quick-fixes-if-your-firefox-slows-down

https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-or-cpu-resources


MemTest Could you please run a tool from http://memtest.org/ in order to check the integrity of your RAM?

You will need a thumb or disk drive to install it on.


Do you let Windows handle the page file or did you set a fixed size ? Control Panel -> System -> Advanced -> Performance -> Settings

If you use a fixed size for the page file then try the former and let Windows handle the page file. How to determine the appropriate page file size for 64-bit versions of Windows {web link}

more options

I have let windows manage the paging, did not sit any limits. I did run a memory test from boot a couple weeks ago, did the long one that took over 2 hours and all was fine. What I haven't done is sent any crash reports, when I get the box that says FF didn't stop and do I want to send a report, I answer no and just run CCleaner and restart. Have not run in safe mode, but have wondered about that tab reload addon, been thinking of stopping one addon at a time to see if the problem goes away. Or maybe stop them all and add one in at a time.

more options

When any program crashes, you should let them send in a crash report. How else can the programmers know there is a problem.


It could be the work of one of your add-ons, or it could be Hardware Acceleration. How to disable Hardware Acceleration {web link}

Type about:addons<enter> in the address bar to open your Add-ons Manager. Hot key; <Control> (Mac=<Command>) <Shift> A)

In the Add-ons Manager, on the left, select Extensions. Disable a few add-ons, then Restart Firefox.

Some added toolbar and anti-virus add-ons are known to cause Firefox issues. Disable All Of them.

If the problem continues, disable some more (restarting FF). Continue until the problem is gone. After, you know what group is causing the issue. Re-enable the last group ONE AT A TIME (restarting FF) until the problem returns.

Once you think you found the problem, disable that and re-enable all the others, then restart again. Let us know who the suspect is, detective.

more options

I had hardware acceleration turned on by default when I checked "use recommended performance settings", will turn that off. I noticed FF no longer has a sitting under "use hardware acceleration when available" for number of content process limit, which had a default of 1 and I think max of 8.

Next time it hangs I will send it in, I am a bit concerned about sending off data, who knows what they really pick up? Always figured it was just sent off to a bit bucket that no one looked at anyway. I guess after 34 years as a programmer and system software tech, I am cautious. Just because it displays one thing doesn't mean it really does it. Been retired now for 17 years.