This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

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.

Rohkem teavet

Firefox auto-updated to 58.0.1 now it's unresponsive and hangs drastically with 4 processes running

more options

So today Firefox auto-updated from 58.0 to version 58.0.1 and now it is totally unresponsive. when i open firefox nothing happens for at least 15 secs then it finally opens if I click on anything or try to open another tab it hangs (with the firefox is not responding in the header bar) for 15-20 sec then finally does something. Also before the update I only ever had 1 firefox.exe process ever running now I have at least 4!!

So today Firefox auto-updated from 58.0 to version 58.0.1 and now it is totally unresponsive. when i open firefox nothing happens for at least 15 secs then it finally opens if I click on anything or try to open another tab it hangs (with the firefox is not responding in the header bar) for 15-20 sec then finally does something. Also before the update I only ever had 1 firefox.exe process ever running now I have at least 4!!

All Replies (1)

more options

Hi madmaniakid, sorry to hear about these problems. There were only a small number of changes in the 58.0.1 update compared with 58.0, so hopefully that will help in tracking down the problem.

It's normal to see several firefox.exe processes in the Task Manager in Firefox 54 and higher. These include one to two user interface processes, and up to four content processes. When Firefox works well enough to use the Options page, you can reduce the number of content processes if you like. See: Firefox's performance settings. However, I don't know whether that will make any difference.

Could you test in Firefox's Safe Mode? In Safe Mode, Firefox temporarily deactivates extensions, hardware acceleration, and some other advanced features to help you assess whether these are causing the problem.

If Firefox is not running: Hold down the Shift key when starting Firefox.

If Firefox is running: You can restart Firefox in Safe Mode using either:

  • "3-bar" menu button > "?" button > Restart with Add-ons Disabled
  • Help menu > Restart with Add-ons Disabled

and OK the restart.

Both scenarios: A small dialog should appear. Click "Start in Safe Mode" (not Refresh).

Any improvement?