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

After Firefox update it takes up to 10 minutes for the browser to become responsive.

  • No replies
  • 0 have this problem
  • 1 view

OS: Xubuntu 24.04.2 Apache: 2.4.58 Firefox 137.0.1 and earlier

In general Firefox is working. However, after every update, both major as well as point releases, where Firefox updates and then restarts itself, it almost always starts up and displays the homepage (local page on my machine) but is completely unresponsive. It will not load a locale or a remote page. I can kill all running firefox processes and then manually restart the browser -- with the same behavior. I have discovered that if I wait for around 10 minutes or so, then the browser starts working and continues to work just fine until the next update. Once past this initial update wait, I can kill/restart the browser, reboot, etc. and Firefox is responsive. It is only immediately after the updates that this problem occurs. This has been going on for at least the past six months or so, but is new behavior that didn't exist prior to that. This isn't a show-stopper, but it is very frustrating.

Any suggestions.

OS: Xubuntu 24.04.2 Apache: 2.4.58 Firefox 137.0.1 and earlier In general Firefox is working. However, after every update, both major as well as point releases, where Firefox updates and then restarts itself, it almost always starts up and displays the homepage (local page on my machine) but is completely unresponsive. It will not load a locale or a remote page. I can kill all running firefox processes and then manually restart the browser -- with the same behavior. I have discovered that if I wait for around 10 minutes or so, then the browser starts working and continues to work just fine until the next update. Once past this initial update wait, I can kill/restart the browser, reboot, etc. and Firefox is responsive. It is only immediately after the updates that this problem occurs. This has been going on for at least the past six months or so, but is new behavior that didn't exist prior to that. This isn't a show-stopper, but it is very frustrating. Any suggestions.

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.