I've got a Firefox process with nothing in it but the Google home page (the "search" page, not the "homey" home page with news etc.) and this site. I've killed it and restarted it multiple times. It's burning massive amounts of CPU cycles doing ... what?
I notice that Firefox, over time, leaks memory terribly and uses more and more CPU, but not anything close to this much. What is it doing?
Mozilla released Firefox 13 Wednesday, which it says is a speedier, safer version of the open source web browser. The newly launched Firefox also boasts a new home page and tab page layout similar to those of competing browsers such as Google's Chrome.
As superuser I reinstalled firefox in terminal (yum reinstaall firefox)
this did not change the behavior of firefox--still unusable, but if I run firefox from a superuser terminal (or with sudo) It works fine.
Attached are screenshots of a page working (SuperUser) and the same page not workint (normal us
Suddenly Fire Fox is bust! Ironically I just read page "Even Firefox has bugs". First manifested when I tried to go to Googlemail, clicking on bookmark, showed an Apache2 error page and a Centos info which seemed like an amusing insight into Google looking like an outage.
I have come up against a problem that seems to make Firefox in F11 nigh-on unusable.
As soon as I open any page that is of moderate size and or has plenty of pictures (take a forum like this with a thread that has a full page of responses to a question), the CPU usage of Xorg and firefox processes go through the roof.
I'm seeing weirdness with Scottrade's main screen with Firefox (not the real-time streaming quotes app). It seems after a few minutes, whether idling or otherwise, Firefox gets into a state where nothing on the Scottrade page is clickable. Firefox menus still work as do other tabs so Firefox itself is still alive. It's as if a timer fires inside Firefox that renders the Scottrade page inert.