I have noticed that something is overall WRONG with FF since their last update. Specifically, it suddenly bogs down my computer, both when running as a PC or as a Mac. It causes the system processes to spike and causes enormous lag in the entire system.
Certain sites then cause FireFox to refuse to close once you visit them. In other words, FirFox appears to have closed but is actually still running and using vast system resources in the background. The only way to actually quit FireFox is to force close the program. It has been so bad in fact that I don't have much choice but to start using a different browser. Has anyone else encountered this problem?
It seems to be a cumulative problem - the longer FireFox is allowed to run the more intense the CPU usage spikes and the worse the overall lag becomes. It is even happening as I am on this (the FireFox) site for the length of time it has taken to write all this.
所有回覆 (9)
If you start Firefox in Safe Mode, then try to visit those websites, does it still freeze? What are some of those websites if you don't mind posting them.
Does Firefox consumes a lot of CPU resources help?
I have not tried safe mode yet, but will. And it appears to be essentially all sites really - the longer I'm on, the worse the resource consumption. When I close FireFox it actually continues running (and using alllll those resources) in the background until actually force closed. It does that no matter what site(s) I visit, or even if I I simply open it, then close it. Even being on this site for these few minutes is showing a lag beginning as resources are brutally absorbed. It does this regardless of the platform. If it has one, four or even more MB of memory to work with, it simply keeps taking more until even my macbookpro is crawling within about 30 minutes. I'm going to have to switch to Chrome or Opera soon.
Ok, usually Firefox not closing down is caused by a faulty addon, so hopefully Safe Mode will correct that. If it does, we will want to narrow down what exactly is causing the problem so we can remove it from your computer.
1 or 4 MB of RAM is extremely little. Right now, running Firefox 10, I'm using 178.72 MB, and I've got lots of addons and windows open.
Test with safe mode, and if that does help, we will narrow down from there, if not, I've got a few other things we can test ;)
Sorry, I meant 1 -4 GB of RAM. =) I am actually at work trying this on my work computer, and indeed safe mode seems to help a bit... but I'm uncertain which plugin is causing the problem. Though I suspect it is GreaseMonkey. Things certainly ran better once all the add ons were disabled.
When I have a bit more time I will start picking through the add-ons here, however I am far more concerned about my home laptop, so later tonight I will sit down with all of this and really start trying to figure out the issue.
LOL, I suspect I'll be adding lots of questions/observations at that point. Thanks for your help so far and I'm sure I'll need more once I'm up to my eyes in sorting through my MacBook...since I run it as both a Mac and as a W7 PC. So I'll have twice the work sorting it all out.!
It is appearing to be something to do with GreaseMonkey. I will have to explore further, but my work PC definitely shows heavy memory usage when GM is enabled. One site that causes FireFox to fail to shut down, with or without GM running is the online game KOL (Kingdom of Loathing). I will be trying to sort these issues out on my home computer now also. Will update as things develop.
See also:
- "Hang at exit": http://kb.mozillazine.org/Firefox_hangs
- "Firefox hangs when you quit it": https://support.mozilla.org/kb/Firefox+hangs
I have now done pretty much every suggestion that even vaguely applies in the various helpful link provided. Thanks for the ongoing help. =)
I have managed to get FireFox's start-up memory usage down to about 100,000K, however it appears that memory usage keeps creeping up the longer FireFox is open. (It seems to top out around 500,000K.) And I'm not talking open for many hours or days - but rather for minutes and possibly up to a couple hours. (Based on how long I've been fiddling with all this so far.)
On the plus side, it does not appear GreaseMonkey is the culprit since with it active or disabled this memory creep still occurs. Although having GreaseMonkey enabled definitely increases the rate of memory creep. Though once it has creeped up to 150,000+K, disabling GM does not make it drop back down to the starting 100,000K.
I should point out I run a MacBook Pro and use Bootcamp to partition the hard drive and run it as a Windows 7 PC about half the time. I am running it literally as a PC or, alternately, as a Mac depending on which hard drive I choose to load. (I'm not "windowing" it.) This problem exists regardless of whether I am using the PC or the Mac. These repairs have been made currently on the PC side, and I will attempt them all again on the Mac side. I find it odd that this enormous memory drain has occurred on 3 different computers at the same time. (The two "halves" of my home laptop as well as the PC at my work place.)
Well, I'm ready to give up. The problem is "manageable" on the PC, though not apparently fixable. It is an unholy mess on the Mac. Part of this could be since I am less familiar with the nuances of Macs, part may be that the fact that the help guides all are aimed at PC users, and part may just be the latest build of FF just plain old sucks with Mac. I dunno. FF is using VAST amounts of the CPU - from 6% to as much as 90+% from one second to another. It's jumping all over. And this is with having cleaned up the plug ins and done all the other suggestions that even vaguely were applicable.
You can check the about:memory page to see the current memory usage.