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

Why does Firefox 53.03 ramp up my CPU usage 60 seconds after opening and at completely random times?

  • 7 replies
  • 3 have this problem
  • 5 views
  • Last reply by FredMcD

more options

Approx. 60 seconds after opening Firefox 53.03 my CPU usage ramps up to 15% and Firefox gains 300 - 500 MB memory for 10 - 30 seconds.

This occurs at random times as well.

This only happens with Firefox 53.03 and no other version prior.

This has happened to every machine I've installed it on.

Approx. 60 seconds after opening Firefox 53.03 my CPU usage ramps up to 15% and Firefox gains 300 - 500 MB memory for 10 - 30 seconds. This occurs at random times as well. This only happens with Firefox 53.03 and no other version prior. This has happened to every machine I've installed it on.

Chosen solution

It could be the work of one of your add-ons. 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.

Read this answer in context 👍 0

All Replies (7)

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


Try to disable multi-process tabs in Firefox. You can disable multi-process tabs in Firefox by setting the related prefs to false on the about:config page.

browser.tabs.remote.autostart = false browser.tabs.remote.autostart.2 = false

http://www.ghacks.net/2016/07/22/multi-process-firefox/

Type about:config<enter> in the address bar. If a warning screen comes up, press the Be Careful button. At the top of the screen is a search bar.

more options

Made the change, verified the change took, but still have the problem.

I don't have to do anything but open FF53 stare at the screen on any tab, even a blank tab with Task Manager open and 60 seconds later, FF starts ramping CPU and memory for 10 - 30 seconds.

Does it at random times without any actual browsing or even in focus.

FF53 just has to be running.

Does it on all of my machines.

I'm running 32 bit viewer on 64 W7 OS, but does it on 32 bit W7 OS, too.

FF52 and prior didn't have this issue.

Thanks for the help, though.

Modified by tempaccount

more options

Start Firefox in Safe Mode {web link} by holding down the <Shift> (Mac=Options) key, and then starting Firefox.

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

more options

In safe mode it ramps CPU only for 1 - 2 seconds with no memory increase.

more options

Chosen Solution

It could be the work of one of your add-ons. 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

Thanks Fred, this seems to be an issue with Adblock Plus that is causing it as it does not occur when I disable it and reopen the browser.

Enabling it causes an intial ramping of cpu an memory for a second, but the 10 second long ordeal happens 60 seconds later.

I will continue my enuiry on ABP's forum.

Thanks again.

more options

Glad to help. Safe Surfing.