Closed
Bug 44204
Opened 25 years ago
Closed 25 years ago
Mozilla crashes (sometimes taking system down with it) when clicking on an <A href="javascript:Function()"> which calls a function that sets window.location to itself
Categories
(Core :: DOM: Navigation, defect, P3)
Tracking
()
People
(Reporter: lobotomy42, Assigned: warrensomebody)
Details
(Keywords: crash)
Attachments
(1 file)
|
205 bytes,
text/html
|
Details |
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; m17) Gecko/20000628
BuildID: 2000062808
When accessing a javascript function which sets window.location to equal
window.location (or in any way set window.location to the same url that the
window is currently at) through the <xmp><a href="javascript:function()"> </xmp>
method, Mozilla totally freezes and stops responding. Quite often, the entire
system does as well, forcing a hard reboot. In Netscape 3+, and IE4+, the page
simply reloads as I presume it is supposed to. This does not seem to happen when
the function is called using buttons or the onclick event in a link.
Reproducible: Always
Reproduce:
Click on link which, through javascript: in href attribute, calls a function
that sets window.location to what it already is.
Actual Results: Browser freezes totally, sytem stops responding (sometimes,
other times I can Ctrl+Alt+Del out).
Expected Results: The page containing the link should reload.
Test case: Make a page like this:
<xmp>
<html>
<Script>
<!--
function ReDoPage1() {
window.location = window.location
}
// -->
</script>
<body>
<a href="javascript:ReDoPage1()">window.location=window.location</a><br>
</body>
</html></xmp>
|
Reporter | |
Comment 1•25 years ago
|
||
Ignore <xmp> tags in above html block.
|
||
Comment 2•25 years ago
|
||
|
|
||
Comment 3•25 years ago
|
||
The freeze is already known (see bug 37463, I verified that this testcase has
the same stack traces). I don't know if this bug should remain open for the
remaining issue ("taking system down with it").
|
|
Reporter | |
Comment 4•25 years ago
|
||
My guess would be not to leave it open. What happens specifically is that
Mozilla hangs, and then when I try to use Ctrl+Alt+Del to End Task (in Win98), I
get Mr. Blue Screen of Death and then it stops responding. So the problem of
the system hanging is more likely some Windows error in trying to close Mozilla
once it hangs, IMHO.
|
||
Comment 5•25 years ago
|
||
Since it's not a JS Engine bug, reassigning in a way consistent with bug 37463 -
Assignee: rogerl → warren
Component: Javascript Engine → Embedding: Docshell
QA Contact: pschwartau → BlakeR1234
|
||
Comment 6•25 years ago
|
||
I think this is just a dup of 37463...we'll recheck this when that's fixed.
Some systems might handle crashes and freezes differently, depending on amount
of memory available, and so forth.
*** This bug has been marked as a duplicate of 37463 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•