http://bugzilla.novell.com/show_bug.cgi?id=561217 http://bugzilla.novell.com/show_bug.cgi?id=561217#c0 Summary: Firefox 3.5 in GNOME causes Xorg to CPU hog when visiting certain websites Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome@forge.provo.novell.com ReportedBy: rdb@ccb.ac.uk QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.5) Gecko/20091103 SUSE/3.5.5-3.1 Firefox/3.5.5 Firefox 3.5 causes the Xorg process to CPU hog (very high CPU utilisation) for either a number of seconds, or indefinitely, depending on the website and/or the GPU in use. The high Xorg CPU utilisation slows down or hangs both Firefox and other running Gnome applications, making the system all but unusable until the Tab or browser window containing the website is closed. Websites which certainly cause this issue include some Image hosting websites and the Groupwise 7 WebAccess web interface (when using the full interface in broadband or dialup mode - it does not occur on the simple version) It seems the problem is specific to javascript 'heavy' websites as all the triggering sites witnessed use Javascript to resize images and/or manipulate the location and layout of the site. It seems the problem occurs consistently and most noticeably on machines with NVIDIA GPU's running Nvidia's proprietary driver and default Xorg.conf. This has been reproduced on 3 out of 3 attempted NVIDIA workstations, using a GTX260, GT210, and a 7600 GPUs. During testing, all 3 machines have been freshly re-installed from the DVD, with only patches and the Nvidia driver installed, and the problem still occurred. The problem has also been reproduced on a Intel GM965 GPU (but with much briefer disruption, the Xorg spikes lasting less than second each time) This bug has only been witnessed and tested on 64-bit workstations. I am unsure whether or not the issue occurs in 32-bit installs. Compiz being turned on or off doesn't have any impact on this issue. The problem does NOT occur initially after a fresh boot of 11.2 with Gnome 2.28. Firefox can be used to visit these sites repeatedly without issue after an initial boot. Xorg utilisation is no higher than 6% visiting triggering sites after a fresh boot. However, the problem emerges instantly, with 100% reproducibility and up to 100% CPU util by Xorg after loading up Pidgin. Closing Pidgin does not stop the problem occurring, the issue will happen in GNOME until the machine is restarted. I am not sure if Pidgin is the only application that triggers this issue, or whether it is something more generic with other GTK-based apps triggering the issue. The problem occurs in both the standard 11.2 version of Firefox, but also with the versions of Firefox in the OpenSUSE Build Service Mozilla repo and the upstream tar.gz packaged version from www.mozilla.com The problem does not occur visiting the same websites in other browsers, such as Opera. The problem does not occur, under any circumstance, under KDE 4.3 on 11.2. Even on the same machine, same drivers and same xorg.conf and loading up Pidgin, Firefox in KDE does not have this issue. With all these issues considered, I have filed it as a GNOME bug, and not an X11, Pidgin, or Firefox issue. I have attached the following in the XorgFFBug.zip file: Xorg.conf - a Xorg.conf from a effected machine with an NVIDIA GPU produced by nvidia-xconfig as part of the Driver installation GnomeFFAllOkay.jpeg - Firefox in Gnome having no problem while visiting a javascript heavy website after a fresh reboot. Top showing the CPU usage. GnomeFFAfterPidgin.jpeg - Firefox in Gnome having the issue while visiting the same website after loading pidgin. Top showing the CPU usage. GnomeFFEvenAfterPidginClosed.jpeg - Firefox in Gnome having the issue while visiting the same website after loading pidgin and then closing it. Top showing the CPU usage. KDEFFOkay.jpeg - Firefox in KDE having no problem while visiting a javascript heavy website after a fresh reboot. Top showing the CPU usage KDEFFAfterPidgin.jpeg - Firefox in KDE having no problem visiting the same website after Pidgin has been rebooted. Top showing the CPU usage Reproducible: Always Steps to Reproduce: 1. Have a machine with an NVIDIA GPU, using the 1-click driver install from www.opensuse.org wiki 2. Open Firefox, access a website that triggers this issue (eg. Groupwise 7 Webaccess) 3. Open Pidgin 4. Refresh the page, or switch to a different tab and back to the tab containing the trigger website. 5. Watch Xorg's CPU usage jump sky high. Actual Results: Xorg uses extraordinarily high amounts of CPU, slowing down the workstation to an unusable crawl, with everything from website rendering to application loading being much much slower then usual. Expected Results: Not used lots of CPU -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.