Red Hat Bugzilla – Bug 442860
Gecko engine and X -> high load
Last modified: 2008-09-18 12:46:08 EDT
Description of problem:
Rendering some websites using Gecko (Firefox & Epiphany) causes the X-Server to
have extremely high cpu usage.
Tested with http://nooners.de which causes firefox between 60% and 100% of cpu
usage, while konqueror renders smoothly with 5%-10%.
This happens on my notebook with ATI x1400 (fglrx, radeon, radeonhd tested) and
on my desktop (nvidia) - so its propably not a driver/hardware thing.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. open firefox
2. open top
3. surf to a site where images are moving around (e.g. http://nooners.de - this
site brought me to that bug, as I wrote it ;) )
X turns to use up to 100% of CPU
X should not use more than 10% especially with DRI activated
This site runs fine on some debian systems (using ff2 & ff3)
ii xserver-xorg 1:7.2-5 the X.Org X server
ii iceweasel 188.8.131.52-1 lightweight web browser based on Mozilla
Thanks for the bug report. We have reviewed the information you have provided
above, and there is some additional information we require that will be helpful
in our diagnosis of this issue.
Please attach your X server config file (/etc/X11/xorg.conf) and X server log
file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file
attachments using the bugzilla file attachment link below.
Could you please also try to run without any /etc/X11/xorg.conf whatsoever and
let X11 autodetect your display and video card? Attach to this bug
/var/log/Xorg.0.log from this attempt as well, please.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Sorry for the late response, I simply forgot about that issue, as the combination of f9/new laptop/ff3 fixed it for me.
For you information here is my xorg.conf.
Created attachment 316360 [details]
xorg.conf from fedora 8
(In reply to comment #2)
> Sorry for the late response, I simply forgot about that issue, as the
> combination of f9/new laptop/ff3 fixed it for me.
> For you information here is my xorg.conf.
Cool, so does it mean that you could close this bug as fixed somewhere in F9 range?
I think NEXTRELEASE should be the correct reason to close this bug.