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

Cuireadh an snáithe seo sa chartlann. Cuir ceist nua má tá cabhair uait.

Why does Firefox version 23.0 for desktops continually use 1.8 GB of memory and more than 50% of the CPU from the moment I start it and eventually hangs?

  • 1 freagra
  • 5 leis an bhfadhb seo
  • 3 views
  • Freagra is déanaí ó John99

makemyday
makemyday
more options

All versions of Firefox subsequent to version 3.5 would hang regularly after several minutes of inactivity (I have yet to see an explanation for this). I continued using version 3.5 until Mozilla dropped support for it, which I believe was when they released version 5 or 6, at which time I started installing all new versions. Now with version 23.0, Firefox eventually hangs while using it and can only be terminated via the Task Manager or Process Explorer. Also, version 23.0 continually uses 1.8 GB of memory and more than 50% of the CPU from the moment I start it (my start page is the Firefox start page), even if I do nothing else after start-up. I got so fed up with version 23.0 that I uninstalled it after trying to use it for several hours. I reinstalled version 22.0, but the exact same hanging, memory usage, and CPU problems associated with version 23.0 have somehow now carried over to version 22.0.

So I researched what I could possibly do to resolve the problems I'm having with Firefox. Mozilla recommends either starting Firefox in Safe Mode to troubleshoot potential issues with extensions, themes, and hardware acceleration or resetting Firefox via the Reset Firefox feature. Both recommendations require a lot of unwarranted time and effort without any guarantee that anything will be accomplished by either recommendation other than possibly exposing bugs in Firefox. Besides, my add-ons didn't affect any Firefox versions prior to version 23.0, so why should they be a problem with version 23.0? Furthermore, following Mozilla's recommendations wouldn't explain why the hanging, memory usage, and CPU problems associated with version 23.0 are now affecting version 22.0 and why versions prior to the release of version 23.0 didn't have these problems.

For now, I just want to be able to roll back to version 22.0 without all of the attendant problems of version 23.0 and without Firefox being able to automatically update it to version 23.0, or any later version for that matter. Until that happens, Firefox is unusable for my purposes with all of the problems triggered by version 23.0. (Recent versions of Firefox prior to version 23.0 have introduced new problems that I'm not going to get into at this time as long as I am experiencing the latest problems with Firefox.)


My system environment:

I have a Dell XPS 400 desktop computer with Intel Core 2 Duo processors (Intel Pentium D CPU 2.80GHz), 3.00 GB of RAM, and a 250 GB hard drive. My operating system is Windows XP, Media Center Edition, Version 2002, Service Pack 3.

All versions of Firefox subsequent to version 3.5 would hang regularly after several minutes of inactivity (I have yet to see an explanation for this). I continued using version 3.5 until Mozilla dropped support for it, which I believe was when they released version 5 or 6, at which time I started installing all new versions. Now with version 23.0, Firefox eventually hangs while using it and can only be terminated via the Task Manager or Process Explorer. Also, version 23.0 continually uses 1.8 GB of memory and more than 50% of the CPU from the moment I start it (my start page is the Firefox start page), even if I do nothing else after start-up. I got so fed up with version 23.0 that I uninstalled it after trying to use it for several hours. I reinstalled version 22.0, but the exact same hanging, memory usage, and CPU problems associated with version 23.0 have somehow now carried over to version 22.0. So I researched what I could possibly do to resolve the problems I'm having with Firefox. Mozilla recommends either starting Firefox in Safe Mode to troubleshoot potential issues with extensions, themes, and hardware acceleration or resetting Firefox via the Reset Firefox feature. Both recommendations require a lot of unwarranted time and effort without any guarantee that anything will be accomplished by either recommendation other than possibly exposing bugs in Firefox. Besides, my add-ons didn't affect any Firefox versions prior to version 23.0, so why should they be a problem with version 23.0? Furthermore, following Mozilla's recommendations wouldn't explain why the hanging, memory usage, and CPU problems associated with version 23.0 are now affecting version 22.0 and why versions prior to the release of version 23.0 didn't have these problems. For now, I just want to be able to roll back to version 22.0 without all of the attendant problems of version 23.0 and without Firefox being able to automatically update it to version 23.0, or any later version for that matter. Until that happens, Firefox is unusable for my purposes with all of the problems triggered by version 23.0. (Recent versions of Firefox prior to version 23.0 have introduced new problems that I'm not going to get into at this time as long as I am experiencing the latest problems with Firefox.) My system environment: I have a Dell XPS 400 desktop computer with Intel Core 2 Duo processors (Intel Pentium D CPU 2.80GHz), 3.00 GB of RAM, and a 250 GB hard drive. My operating system is Windows XP, Media Center Edition, Version 2002, Service Pack 3.

All Replies (1)

John99
John99
more options

Hi musicfan,
Sorry you are having problems with Firefox. Maybe you should have asked earlier and we could have fixed it.

Reading your comments I do not see that rolling back to an insecure Firefox 22 will actually help you much. You are probably best using IE, unless you have also damaged that.

You should not use old versions they are insecure. Security fixes are publicised and exploitable.

Most others will not be having such problems. We are now able to say that with confidence because after developers missed a regression in Firefox 4 telemetry was introduced so that data was obtained. It may be an idea to turn on your telemetry, if you have not already done so, and decide to stick with Firefox.

Trying safe mode takes seconds. Unfortunatly if you are not willing to do even rudimentary troubleshooting there is not anything we can do to help you.