265153 - 100% CPU Usage When Opening URL --> Prior to Receiving Any Data

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[Mark P. Peterson]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040916 Firefox/0.10.1 (mmoy-Release10pr-Pentium-4U)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040916 Firefox/0.10.1 (mmoy-Release10pr-Pentium-4U)

CPU goes to 100% after connecting to a proxy server or attempting to connect to
a web site directly.  CPU usage in browser doesn't go down to appropriate levels
until data is actually returned back to the browser.  This causes very sluggish
system operation under Windows until data is sent to the browser.

Reproducible: Always
Steps to Reproduce:
1. Open Task Manager
2. Sort by CPU usage
3. Visit a URL

Actual Results:  
CPU becomes pegged at 99-100% until browser receives data.

Expected Results:  
Software shouldn't be in a loop waiting for the initial data.

Using the proxy server I've developed I can confirm that the browser receives
the FD_CONNECT, but appears to be stuck in a loop waiting for data.  If instead
of looping the browser went back into Windows message loop, being woke up on
FD_RECEIVE this problem shouldn't happen.  As it is now the CPU becomes pegged
making Windows and all other applications sluggish, if accessible at all.

Comment 1

[Boris Zbarsky [:bzbarsky]]

Is this a problem in a current trunk build?

Comment 2

[Bill Wallace]

No, this is no longer a problem in the current trunk build.  I had observed this
multiple times with previous builds, and I haven't yet observed it in 10/27/04
build.

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.