242129 - infinite requests sent to websever after page is loaded 100% cpu usage - freezer

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[Girish Patangay]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040206 Firefox/0.8

We have our own HTTP server used in our embedded devices. When I goto the page,
it's going in an infinite loop with "GET" requests. The requests are for the
same page. Note: It loads the page before going into the loop. Another problem
is that the CPU usage is 100% and Mozilla stops responding. Pressing ESC or Stop
button relieves some pressure, but the CPU usage still remains at 100%.

Reproducible: Always
Steps to Reproduce:
Just accessing the website gives this error, you can find an ethreal capture of
this at the following address:
http://support.intoto.com/mozilla_loop.cap
Actual Results:  
CPU Usage 100%
Browser keeps sending Get Requests for the same page
Browser Not Responding


Expected Results:  
It should have loaded the page and stopped.

Comment 1

[R.K.Aa.]

does it also happen with a new Mozilla-profile?

Comment 2

[Girish Patangay]

Yes. It happens on a new profile and also I have tried Mozilla, Firefox on both
Linux and Windows

Comment 3

[Boris Zbarsky [:bzbarsky]]

Not much we can do about this without the source of the page in question.....
(use http://bugzilla.mozilla.org/attachment.cgi?bugid=242129&action=enter to
attach files to the bug).

Comment 4

[Girish Patangay]

Attachment: Files that crash mozilla

These are the files that will crash mozilla from both local and remote view.

I know its something to do with the javascript, espically the layers code.

There is another directory in the zip file called "diff" that contains the code
that does NOT crash the browser.

I think it's just poor programming on the programmers part here, but it still
shouldn't kill the browser.

Girish

Comment 5

[Girish Patangay]

FYI, in case I failed to mention. That same page works in IE without problems.
Which is what our people seem to use to test these pages, but I made them also
test in mozilla, which is how I find the problem.

Comment 6

[R.K.Aa.]

Attachment: some stepping through gdb

confirming freeze and high CPU usage w/current trunk, Linux.
Broke it in gdb when the freeze was a fact, backtraced and then stepped as far
as i got before the freeze got the better of me. Non-debug - FWIW.

Comment 7

[Jesiah S]

It crashed on me LInux 2004061405
TB94460K

Comment 8

[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 9

[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.