165343 - Simultaneous reloads cause high CPU usage that doesn't restore

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect)

Description

[jsoffer]

While browsing some apparently random circunstance causes the client to use more
that 90% of the CPU that doesn't goes back to normal levels. It may be related
to bugs 164170 and 164547. It is nasty because forces a restart of the browser
and some slugginess of the system in general.

The steps that work almost flawlessly to reproduce the bugs are (javascript
disabled):

1. Open http://www.opengl.org/discussion_boards/ubb/Forum4/HTML/000683.html on
the default tab. Stop the load with Esc.

2. Open a new tab and load http://www.explicia.com/dragon/hito001.html
on it. Stop the load too.

3. Click at and forcely reload (Control-Shift-R) the first tab.
4. Reload the second tab the same way.

5. Keep reloading both tabs until the CPU load rises. It may take between two
and six reloads. Wait between one and three seconds between reloads.

Keep an open terminal with top running at an interval of 0.3 seconds to know
when the bug is coming into play.

When the bug happens, at my machine (Linux Debian woody, PIII 800) it takes 93%
of the CPU, and keeps like that even if I open a new, empty tab and close the
other two.

I suspect that it is a problem with threadings, but can't test it.

This build compiled from the Mozilla1.1beta tarball; I will check later with the
1.1 release.

Comment 1

[jsoffer]

Well, turning off 1.1 pipelining solves the problem... it should be a duplicate
of    bug #146884.

Comment 2

[Benjamin Smedberg]

[e-mail]: can you try this again with a newer version of mozilla
(daily builds are available from the website).  Please also check HTTP
Pipelining (see comment #1).  If this is no longer a problem, please resolve it
WORKSFORME.  Thank you!

Comment 3

[jsoffer]

No longer a problem at Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2a)
Gecko/20020912