Closed Bug 165812 Opened 23 years ago Closed 23 years ago

browser busywaits when accessing a page from a slow server

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Platform:
x86
Windows 2000
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: yurit, Assigned: asa)

References

(
URL
)

Details

when I request a page from a really slow server the browser busywaits while retriving the page. while it makes sense that it would take forever for me to get the page (the server is absolutely overloaded with IO and serves the page at a very slow rate), it seems that this should _not_ push CPU use to 96%, making all other mozilla windows completely unavailable and all non-mozilla windows barely responding. i end up having to kill mozilla through the task manager.
reporter: what is the build ID of the mozilla you are using? what platform are you on? possibly a dupe of bug 91232 or one of the other collection of high CPU usage bugs...
I am using Mozilla 1.1 (build 20020826) on Win2k. The machine is a 500MHz Dell with 655MB of RAM. However, I tried reproducing this bug with simpler cgi scripts (one that just returns one character every second or so), and i don't seem to be able to reproduce this. So, this must be something else. Might be just rendering a big file (1.5 MB), though there seems to be some sort of interaction with how fast the file served. (Normally i can render files of such size without too much trouble.) I will try to come up with a better test case. If i can't do that within a week or so, we might have to close the bug. Generally, all builds that I tried since the 1.0 release seem to be plagued by going into 96% CPU usage every now and then, and there is often no resort other than killing mozilla. However, in most cases it is not clear what triggers it. This affects both the browser and the messenger, in fact it probably happens more often in the messenger.
The browser waits for the images from the slow server, and hangs on a response. Dupe of bug 158383?
Yuri, could you post the url involved, if it's just Netscape-internal?
reporter (Yuri): can you reproduce this bug with a recent build of mozilla (for example, 1.2alpha)? if so, please comment again with details (a test URL, netscape internal or public, would be great). if not, please resolve this bug as WORKSFORME. thanks.
no response from reporter for >30 days. resolving WFM. reporter: if you can reproduce this with a recent build of mozilla, please reopen this bug. thanks.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.