Firefox pegs CPU usage immediately, even in safe mode

Bug #1019708 reported by Mike Hicks
22
This bug affects 5 people
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

After updating to Firefox 13.0.1 (13.0.1+build1-0ubuntu0.11.10.1), the browser immediately starts using large amounts of CPU time (50 to 100%), even if I start the browser in "safe mode" with plugins and other features disabled. CPU usage remains consistently high as I browse around to other places.

My home page is "about:startpage", the Ubuntu standard.

This should not happen. CPU usage should be at or near zero upon loading a simple page like that.

[mike@3po][~]$ lsb_release -rd
Description: Ubuntu 11.10
Release: 11.10
[mike@3po][~]$ apt-cache policy firefox
firefox:
  Installed: 13.0.1+build1-0ubuntu0.11.10.1
  Candidate: 13.0.1+build1-0ubuntu0.11.10.1
  Version table:
 *** 13.0.1+build1-0ubuntu0.11.10.1 0
        500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu/ oneiric-security/main amd64 Packages
        100 /var/lib/dpkg/status
     7.0.1+build1+nobinonly-0ubuntu2 0
        500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in firefox (Ubuntu):
status: New → Confirmed
Revision history for this message
Brian Brazil (bbrazil) wrote :

I'd like to confirm this on 12.04 with 13.0.1+build1-0ubuntu0.12.04.1.

I'm seeing the same from chrome too, which is very odd. A reboot seems to have cleared it, leap second maybe?

Revision history for this message
Mike Hicks (hick0088) wrote :

Thanks. I was beginning to feel a bit silly after a reboot fixed my issue as well. I had first tried restarting my X environment, thinking that some Gnome libraries or protocols might have gotten out of sync somehow. I rarely reboot my machine since issues can normally be resolved through other means.

Revision history for this message
ten (tenpou) wrote :

Big thank you, both of you. I was going crazy trying to find out the cause as I normally reboot only after a kernel update, and that was the last thing on my mind to try it. Fixed for me, too (12.04 / 13.0.1+build1-0ubuntu0.12.04.1).

Revision history for this message
Mike Hicks (hick0088) wrote :

Just since I'm not sure I want to file another bug against something that may be in a library function or system call, I'll note here that mythfrontend and mythbackend processes (from MythTV) were also running hot on a machine I use as a DVR. Those processes are more heavily multi-threaded, so they showed well over 100% CPU usage.

Revision history for this message
Mike Hicks (hick0088) wrote :

This bad behavior seems to have been caused by issues with futex system calls. Here's the most detailed description I've seen so far, including a small test program that can be used to replicate the behavior (I haven't tried it since it modifies the system time):

https://lwn.net/Articles/504658/

Rather than rebooting, simply setting the system time manually or finding some other way to call settimeofday() would have also restored normal behavior.

Revision history for this message
JP Vossen (jp-jpsdomain) wrote :

I had 4 machines affected by this problem, 3x on Ubuntu 10.04 and 1 on 12.04, all with FF 13.0.1. It also seemed like Thunderbird was a problem, though not as bad as FF. Reboots "fixed" them all, but that's very disappointing. Ubuntu/ntp/GNU/Linux should handle time and leap-seconds more gracefully than this... :-( If I wanted to have time problems and have to reboot to fix things, I could run Windows.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.