View Full Version : Firefox and Xorg caused heavy CPU load
hnws
10th October 2009, 08:30 AM
I use the forum patched NV 190.36 driver.
And all the updates from koji and rawhide.
When I was scroll down in the Google Reader, firefox and Xorg process both ocupied 20% of CPU while Chromium got 10% and Xorg 7% under the same situation.
Demz
10th October 2009, 09:30 AM
whats the actual Problem here?
leigh123linux
10th October 2009, 09:50 AM
I get 50 % CPU usage from Xorg and upto 26 % from firefox when scrolling, What did you expect from Rawhide?
P.S It seems to scroll better with compiz running ;) ( the screen refreshes quicker )
hnws
10th October 2009, 09:54 AM
I got at most 20% cpu usage including ff and xorg yesterday before I ran into F12.....
Under the same ff version and NV driver.
And most important is that the scrolling was very sloooow
leigh123linux
10th October 2009, 10:11 AM
I got at most 20% cpu usage including ff and xorg yesterday before I ran into F12.....
Under the same ff version and NV driver.
And most important is that the scrolling was very sloooow
As I said, what did you expect from a alpha/beta O/S
http://fedoraproject.org/wiki/Schedule
It will improve when the extra kernel debugging is removed.
Demz
10th October 2009, 10:28 AM
isnt fedora always alpha/beta though :D
marko
10th October 2009, 08:23 PM
I got at most 20% cpu usage including ff and xorg yesterday before I ran into F12.....
Under the same ff version and NV driver.
And most important is that the scrolling was very sloooow
Maybe you could try turning off smooth scroll
Edit -> Preferences -> Advanced -> General
uncheck Use smooth scrolling
hnws
10th November 2009, 01:06 PM
Now, the beta testing will jump to the end.
And with kernel 2.6.31.5-127 x86_64 from koji, xorg-server 1.7.1-7 from koji and firefox 3.5.5, the problem remains.
Nvidia 8600M GS with 190.42 binary driver and compiz.
If I turn on the smooth scrolling in firefox, the scrolling will be very slow and lag. Meanwhile firefox and xorg process both can occupy more than 25% CPU.
However, the problem had never happened in F11.
vBulletin® v3.8.7, Copyright ©2000-2013, vBulletin Solutions, Inc.