Closed
Bug 158456
Opened 22 years ago
Closed 17 years ago
URL DOSs Mozilla
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: mozilla, Unassigned)
References
()
Details
Attachments
(1 file)
|
14.84 KB,
image/png
|
Details |
Happens also on Linux
Going to the URL will hose Mozilla. Seems to open fine in IE6. Hangs NN4 also. Don't even know where to start. Assuming it's a JS problem, but no debugging to know for sure.
|
||
Comment 1•22 years ago
|
||
Happens also with Mozilla 1.1a+ Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1a+) Gecko/20020714 I was unable to use Back to ge previous page (or to any page) and also selecting from drop down menu from Back button did not helped. I was forced to restart Mozilla. After going page on status bar there readed "Stopped". And mozilla icon did not shown. It seemed that mouse cursor was flashing fast. Perhaps mozilla was redrawing?
|
||
Comment 3•22 years ago
|
||
There is a simple loop but it doesn't hang my Mozilla. (win2k build 20020720) Reporter : Always add the build ID in a bug report !
|
||
Comment 4•22 years ago
|
||
I think that this is a cookies problem.
The source of the page is:
<html>
<head>
<title>Welcome!</title>
</head>
<body>
<script language="javascript">
<!--
function reload() {
document.location.href="cookiecheck.php";
}
immerreloaden=window.setInterval("reload()",0);
//-->
</script>
</body>
</html>
Getting the source of cookiecheck.php with putty and without sending cookies
gives a very similar page so it seems to me that cookiecheck is reloading
itself, and due to the bad desing of using JS redirection instead of http ones,
Mozilla doesn't applies the redirection limit
|
||
Comment 5•22 years ago
|
||
This is not a JavaScript Engine issue; reassigning to DOM Level 0 -
Assignee: rogerl → jst
Component: JavaScript Engine → DOM Level 0
QA Contact: pschwartau → desale
|
|
||
Comment 6•22 years ago
|
||
This hangs my Mozilla trunk binary 20020715xx on WinNT.
The problem is
function reload()
{
document.location.href="cookiecheck.php";
}
immerreloaden=window.setInterval("reload()",0);
The setInterval() function is designed to keep calling the function
you specify at the interval you specify. In this case, it is going
to keep calling the reload() function every 0 ms. This keeps Mozilla
busy in the equivalent of an infinite loop.
(Note the distinction between setInterval() and the more commonly-seen
setTimeout(). The latter will only call the specified function once.)
This looks like it could be another duplicate of bug 13350,
"DOM needs to police JS infinite loops, schedule garbage collection"
On the other hand, note bug 123273, marked as Verified Fixed:
"setTimeout(something, 0) causes 100% CPU constant"
When I load the given URL, my CPU is at 100% and Mozilla is
unresponsive. No matter how many times I try clicking the "Stop"
button, it keeps going.
True, my build is five days old, but is bug 123273 really fixed, then?
|
||
Comment 7•22 years ago
|
||
Hmm... is the problem that the location change does not clear the SetInterval, maybe?
|
||
Comment 9•17 years ago
|
||
lacks testcase, plus aforementioned bugs are fixed. => incomplete, unless jerry sees WFM with a testcase or feels this is s dupe.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•