Firefox hogs CPU
Hi, Anyone have noticed on SuSE 10.1 when Firefox starts downloading something CPU usage increases to so enormous degree that even stops screen refresh?
Andrei Verovski (aka MacGuru) wrote:
Hi,
Anyone have noticed on SuSE 10.1 when Firefox starts downloading something CPU usage increases to so enormous degree that even stops screen refresh?
Yes, on my laptop. Not on either of my 10.1 desktops though. I haven't had time to figure it out yet. (Firefox 1.5.0x) I ended up switching to Opera 9, but then that hogged up even more CPU time. I just assumed it was due to my overall system. -- K
PerfectReign wrote:
Andrei Verovski (aka MacGuru) wrote:
Hi,
Anyone have noticed on SuSE 10.1 when Firefox starts downloading something CPU usage increases to so enormous degree that even stops screen refresh?
Yes, on my laptop. Not on either of my 10.1 desktops though. I haven't had time to figure it out yet. (Firefox 1.5.0x)
I ended up switching to Opera 9, but then that hogged up even more CPU time. I just assumed it was due to my overall system.
The "cpu hogging" of Firefox was already discussed in this forum under the subject heading of, "bizarre momentary freezes in SUSE 10.1" so go to the archives to see what was said. It all happened ~20th of this month (August). In particular I would install the NoScripts extension for FF. And please read what is stated in the links I gave. Cheers. -- This computer is environment-friendly and is running on OpenSuSE 10.1
Basil Chupin wrote:
PerfectReign wrote:
Andrei Verovski (aka MacGuru) wrote:
Hi,
Anyone have noticed on SuSE 10.1 when Firefox starts downloading something CPU usage increases to so enormous degree that even stops screen refresh?
Yes, on my laptop. Not on either of my 10.1 desktops though. I haven't had time to figure it out yet. (Firefox 1.5.0x)
I ended up switching to Opera 9, but then that hogged up even more CPU time. I just assumed it was due to my overall system.
The "cpu hogging" of Firefox was already discussed in this forum under the subject heading of, "bizarre momentary freezes in SUSE 10.1" so go to the archives to see what was said. It all happened ~20th of this month (August).
In particular I would install the NoScripts extension for FF. And please read what is stated in the links I gave.
Cheers.
Mozillazine reports that there are known memory leak problems (contrary to what some keep saying here). At http://kb.mozillazine.org/Reducing_memory_usage_-_Firefox you can find: Restarting Firefox If you find that Firefox's memory usage continues to grow after long periods of being open, you may want to consider periodically restarting Firefox to bring the memory usage back to reasonable levels. The Session Manager <http://forums.mozillazine.org/viewtopic.php?t=380534> extension allows you to close Firefox while maintaining the pages you have open Memory leaks Memory leaks occur to some extent in Firefox. These memory leaks cause Firefox to not release memory that it is no longer using. 1.5.0.4 fixed several memory leaks. If you have not already, you should upgrade to this release. Because of the concern about memory among users, Mozilla developers have been concentrating more on reducing the leaks, and even have created tools to detect them. So, the Mozilla people "DO" admit to memory leak problems and just because some of you don't see them doesn't mean they aren't there. Jim
Jim Sabatke wrote:
Basil Chupin wrote:
PerfectReign wrote:
Andrei Verovski (aka MacGuru) wrote:
Hi,
Anyone have noticed on SuSE 10.1 when Firefox starts downloading something CPU usage increases to so enormous degree that even stops screen refresh?
Yes, on my laptop. Not on either of my 10.1 desktops though. I haven't had time to figure it out yet. (Firefox 1.5.0x)
I ended up switching to Opera 9, but then that hogged up even more CPU time. I just assumed it was due to my overall system.
The "cpu hogging" of Firefox was already discussed in this forum under the subject heading of, "bizarre momentary freezes in SUSE 10.1" so go to the archives to see what was said. It all happened ~20th of this month (August).
In particular I would install the NoScripts extension for FF. And please read what is stated in the links I gave.
Cheers.
Mozillazine reports that there are known memory leak problems (contrary to what some keep saying here). At
http://kb.mozillazine.org/Reducing_memory_usage_-_Firefox
you can find:
Restarting Firefox
If you find that Firefox's memory usage continues to grow after long periods of being open, you may want to consider periodically restarting Firefox to bring the memory usage back to reasonable levels. The Session Manager <http://forums.mozillazine.org/viewtopic.php?t=380534> extension allows you to close Firefox while maintaining the pages you have open
Memory leaks
Memory leaks occur to some extent in Firefox. These memory leaks cause Firefox to not release memory that it is no longer using. 1.5.0.4 fixed several memory leaks. If you have not already, you should upgrade to this release.
Because of the concern about memory among users, Mozilla developers have been concentrating more on reducing the leaks, and even have created tools to detect them.
So, the Mozilla people "DO" admit to memory leak problems and just because some of you don't see them doesn't mean they aren't there.
Jim
OK, but does this mean that you are not going to upgrade to a later version of FF or not install the NoScripts extension? :-) Cheers. -- This computer is environment-friendly and is running on OpenSuSE 10.1
participants (4)
-
Andrei Verovski (aka MacGuru) -
Basil Chupin -
Jim Sabatke -
PerfectReign