Within minutes [sometimes seconds], Firefox starts using more and more cpu time - up to 95% or more. We have no viruses or other malicious programs running.
I have run multiple virus checkers, cleared caches and cookies, checked for other malware, adware, keyloggers, and have not found anything malicious at all. Rebooting doe… (read more)
I have run multiple virus checkers, cleared caches and cookies, checked for other malware, adware, keyloggers, and have not found anything malicious at all.
Rebooting doesn't stop the CPU hogging. In fact, if you kill Firefox in Task Manager, and the click on "Restore Previous Session", a lot of the time it immediately starts hogging the CPU. Sometimes even with only ONE open tab. Why can't you give us control over active content on a page by page [tab] basis? The universal shut off all active content is NOT a good solution.
Can you not keep active content on a page locked until the user decides to play it [and only have the top tab content be allowed to be active]? Maybe have a specific icon indicating an item wants to run. It's bad enough when the audio from an ad starts playing over the music you were listening to, but this resource hogging, lockup situation has gotten out of hand.
Running all active content on all pages does nothing but diminish the experience for users.
Firefox is my preferred browser, but at this point it runs slower than Explorer, which is beyond sad. It does appear now to have one big similarity to Explorer -- you have been throwing so many patches at it that you have degraded the performance of the program by many orders of magnitude. Some of these patches are probably like Explorer's too -- fixing a problem with a patch that creates other problems that need to be patched which creates other issues, etc, etc, etc.
When I first started using Firefox, it was head and shoulders better than the other browsers. Then you introduced the "plug in container" that really tied resources up -- and still does now from time to time, on top of the other resource hogging. Now you have two instances of Firefox running in Task Manager and both instances want to grab as much CPU time as possible - and in between them they get all available time.
At the very least, give us a way to find and kill off the particular script that is eating the CPU time.
In case you need some system info from us, we are running Windows 7, have a 64bit operating system using an Intel Duo processor at 2.8Ghz, with 4.0Gb RAM.
Any help on how to resolve this would be welcome.