firefox 3 beta 5 on ubuntu 8.04 loads the cPU for 100% for random length of time

[eidam655]

Binary package hint: firefox-3.0

firefox 3 beta 5 on ubuntu 8.04 loads the CPU for 100% for random length of time after the firefox has been launched, and one time or another during the usage. very irritating, as the pc cannot do anything else die to the full CPU load.

Ubuntu 8.04 TLS, kernel 2.6.24.17
firefox-3.0 (3.0~b5+nobinonly-0ubuntu3)

ProblemType: Bug
Architecture: i386
Date: Tue May 6 07:55:07 2008
DistroRelease: Ubuntu 8.04
Package: firefox-3.0 3.0~b5+nobinonly-0ubuntu3
PackageArchitecture: i386
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: firefox-3.0
Uname: Linux 2.6.24-17-generic i686

[Mikael Nilsson (mini)]

Confirmed. The load disappears if I change workspace (!) and returns when I go back to firefox. Note that I see *no* disk activity during this high load.

[Mikael Nilsson (mini)]

Also note that about:blank displays this behavior too, so it's not content-related.

[Armandas (jarusauskas)]

Confirmed once again. High memory usage bursts at random times.

[Brad Johnson (brad-bkjohnson)]

This behavior is also present on a clean installation with no modifications so it isn't caused by any secondary software installations or system modifications.

[Michael Englehorn (michaelje2)]

It seems to be a bug in Java because when I shut Java off it brings processor usage down dramatically.

[TimS (tim-slatcher)]

I am having this problem too, it seems to affect firefox and swiftfox 3 betas. I think I have been experiencing it on Konqueror too, although this could be a result of having firefox running.

[eidam655 (eidam655)]

hm...

i can confirm that whit disabled Java the browser does not do these "CPU leaks," however, as i was logging into this page, the cPU loaded again for 100% immedietely since clicking the Log In button and stopping when page loaded.

[ramki (ramki-s)]

I also see this Firefox 3.0 Beta 5 in Ubuntu 8.04. For me CPU is not hitting 100% yet but its slowly increasing over a period of time. Currently, after 45 mins of usage its about 20%.

Not sure if it helps, upon doing a `strace -p <firefox PID>`, something is going in an infinite loop looks like. Here is the piece of the output.

======================================================
fd=25, events=POLLIN}, {fd=26, events=POLLIN, revents=POLLIN}], 8, -1) = 1
read(26, "\372", 1) = 1
gettimeofday({1210310627, 296794}, NULL) = 0
gettimeofday({1210310627, 296849}, NULL) = 0
gettimeofday({1210310627, 296911}, NULL) = 0
gettimeofday({1210310627, 296961}, NULL) = 0
gettimeofday({1210310627, 297017}, NULL) = 0
read(3, 0x807433c, 4096) = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=12, events=POLLIN}, {fd=3, events=POLLIN}, {fd=17, events=POLLIN|POLLPRI}, {fd=19, events=POLLIN|POLLPRI}, {fd=20, events=POLLIN|POLLPRI}, {fd=21, events=POLLIN|POLLPRI}, {fd=25, events=POLLIN}, {fd=26, events=POLLIN}], 8, 0) = 0
gettimeofday({1210310627, 297253}, NULL) = 0
read(3, 0x807433c, 4096) = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=12, events=POLLIN}, {fd=3, events=POLLIN}, {fd=17, events=POLLIN|POLLPRI}, {fd=19, events=POLLIN|POLLPRI}, {fd=20, events=POLLIN|POLLPRI}, {fd=21, events=POLLIN|POLLPRI}, {fd=25, events=POLLIN}, {fd=26, events=POLLIN, revents=POLLIN}], 8, -1) = 1
read(26, "\372", 1) = 1
gettimeofday({1210310627, 310902}, NULL) = 0
gettimeofday({1210310627, 310978}, NULL) = 0
gettimeofday({1210310627, 311069}, NULL) = 0
gettimeofday({1210310627, 311149}, NULL) = 0
gettimeofday({1210310627, 311232}, NULL) = 0
read(3, 0x807433c, 4096) = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=12, events=POLLIN}, {fd=3, events=POLLIN}, {fd=17, events=POLLIN|POLLPRI}, {fd=19, events=POLLIN|POLLPRI}, {fd=20, events=POLLIN|POLLPRI}, {fd=21, events=POLLIN|POLLPRI}, {fd=25, events=POLLIN}, {fd=26, events=POLLIN}], 8, 0) = 0
gettimeofday({1210310627, 311537}, NULL) = 0
read(3, 0x807433c, 4096) = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=12, events=POLLIN}, {fd=3, events=POLLIN}, {fd=17, events=POLLIN|POLLPRI}, {fd=19, events=POLLIN|POLLPRI}, {fd=20, events=POLLIN|POLLPRI}, {fd=21, events=POLLIN|POLLPRI}, {fd=25, events=POLLIN}, {fd=26, events=POLLIN, revents=POLLIN}], 8, -1) = 1
read(26, "\372", 1) = 1
gettimeofday({1210310627, 366921}, NULL) = 0
gettimeofday({1210310627, 366977}, NULL) = 0
gettimeofday({1210310627, 367038}, NULL) = 0
gettimeofday({1210310627, 367088}, NULL) = 0
gettimeofday({1210310627, 367144}, NULL) = 0
read(3, 0x807433c, 4096) = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=12, events=POLLIN}, {fd=3, events=POLLIN}, {fd=17, events=POLLIN|POLLPRI}, {fd=19, events=POLLIN|POLLPRI}, {fd=20, events=POLLIN|POLLPRI}, {fd=21, events=POLLIN|POLLPRI}, {fd=25, events=POLLIN}, {fd=26, events=POLLIN}], 8, 0) = 0
gettimeofday({1210310627, 367381}, NULL) = 0
read(3, 0x807433c, 4096) = -1 EAGAIN (Resource temporarily unavailable)
poll([{fd=12, events=POLLIN}, {fd=3, eve...

[Andrej Krutak (andree182)]

did anyone have a look on this? It's still happening on my firefox3 too (and that's already a final version) ;-(

[Armandas (jarusauskas)]

Check this: https://bugs.launchpad.net/firefox/+bug/215728/comments/40

[Andrej Krutak (andree182)]

the bug appears (afaik) when one uses too many live bookmarks (10+) - firefox hangs when it's trying to update them.. I moved bookmarks to akgregator instead - no more hangs since then :-) Should be fixed in firefox 3.1 (or later)

[Pablo Castellano (pablocastellano)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. In addition, firefox3 was a beta version but there's some time ago that Ubuntu includes firefox3 final.
We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.