If I visit a link like this http://www.pianetatech.it/hi-tech/elettronica/da-hitachi-i-nuovi-tv-con-triplo-sintonizzatore-per-il-digitale-terrestre.html Xorg eats all my cpu. I have this problem also with Chrome but only if I scrolling the page a lot. I ran Firefox in safe mode disabling all the plugins and addons but the problem still exists. I can reproduce this problem in Firefox 3.6.13+ and 4.0RC2 (didn't try older builds). I use Ubuntu and Xubuntu 10.10 and they are up to date.
At first glance, sounds like a performance bug in your xorg.... did you report it to your distribution?
Component: HTML: Parser → Graphics
QA Contact: parser → thebes
No I didn't but I still think that is a Firefox bug because Chrome is working properly if I don't scroll the page.
That might just be a difference in the exact drawing calls we make, with Xorg having a bug in one of them that we make and Chrome doesn't. Please report this to your distro as well.
UPDATE: I've the same problem (not a Xorg problem) on Windows 7: Firefox.exe takes 50% of my cpu when I visit that page!!! :O
Hmm. I see a bunch of CPU usage on Mac too. roc, the culprit seems to be the news ticker on the right of the page. If I hover it, it stops, and CPU usage plummets. I did a profile, and we're spending time painting text (23%), backgrounds (19%), box-shadows (8%), canvas background (5%), borders (5%), building display lists (7%). Are we ending up painting too much or something? I wouldn't expect that ticker to require that much background painting.
Component: Graphics → Layout: View Rendering
QA Contact: thebes → layout.view-rendering
The ticker is inside a floated div, so because of the float invalidation bug (this code http://mxr.mozilla.org/mozilla-central/source/layout/generic/nsBlockFrame.cpp#2558) we probably end up having to redraw most of the page contents every time the news ticker is updated.
Do we have an existing bug on that? Other than display-list invalidation?
The closest thing we have are bug 119311 and bug 546362, although they aren't about that issue specifically.
Running Firefox 4.0.1 under FreeBSD 8.2 w/ Xorg 7.5.1 Observe same problem on quite a number of pages. Easiest one to duplicate is http://www.yahoo.com Have duplicated while in safe-mode and no plugins. CPU attributed to Xorg rises from approx 3% to 100%. Same page under Opera 11 (FreeBSD version) does not show any abnormal Xorg usage.
Its been about 7 months since I posted (the previous last comment). As an update, this problem still exists on FreeBSD 9.0 Release w/ Xorg server 1.7.7 and Firefox 9, both built through ports. The page that demonstrates this is www.yahoo.com CPU use for Xorg will peg at 100% until either firefox is killed or by luck that tab is killed. I looked at building Xorg 1.10 to see if that would help but as there are a number of other packages also outside of the ports tree I'm going to have to pass as I don't have the technical skills/time to bash my head getting that to work first.
Can't reproduce issue on yahoo, while on original page both Firefox and xorg uses 30% per core Mozilla/5.0 (X11; FreeBSD i386; rv:10.0.2) Gecko/20100101 Firefox/10.0.2
(In reply to Phoenix from comment #11) > Can't reproduce issue on yahoo, while on original page both Firefox and xorg > uses 30% per core > Mozilla/5.0 (X11; FreeBSD i386; rv:10.0.2) Gecko/20100101 Firefox/10.0.2 Since the 2/2/12 post I have moved on to ff 10.0 w/ freebsd 9.0 and the xorg 1.7.7 you appear to be using a beta freebsd? wonder if you have a newer xorg too? also my 100% may be your 30% (older cpu here). Xorg shouldn't be more than a few %, 30% still sounds very high. At this time, the main yahoo page is the only one I have found that brings everything to a screeching halt.
I'm on FreeBSD 9.0 #pkg_version -v | grep xorg xorg-7.5.1 = up-to-date with port But now I remember, this may be Bug 666446, which fixed in FF 11, it will be available in a week, so you can check, if things become better.
Made small test: with originally proposed page Firefox ESR 10.0.3 consuming 30% CPU and xorg uses another 30%, Opera 11 uses near 13% CPU (xorg uses nothing), while Chromium 17 uses only 5-6%(xorg also nothing), so issue definitely still here...
Is this still present in latest Firefox/Xorg versions? Don't have FreeBSD installation with GUI on hardware to retest
Whiteboard: [closeme 2017-05-15]
Resolved per whiteboard
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2017-05-15]
You need to log in before you can comment on or make changes to this bug.