Closed Bug 279666 Opened 21 years ago Closed 21 years ago

Browser exits without cleaning up when running javascript loop

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 271716

People

(Reporter: efrey2, Assigned: bugzilla)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 StumbleUpon/1.999 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 StumbleUpon/1.999 When the browser encounters the code <HTML> </SCRIPT> a = new Array(); while (1) { (a = new Array(a)).sort(); } </SCRIPT> </SCRIPT> a = new Array(); while (1) { (a = new Array(a)).sort(); } </SCRIPT> </HTML> (this is broken on purpose) the browser exits gui but leaves instance running in memory. Any subsequent firefox instances that are run crash imediatly untill the process is kill in the task manager. I will test it tonight on linux to see if I can reproduce it there as well. Reproducible: Always Steps to Reproduce: 1. Write the following code: <HTML> </SCRIPT> a = new Array(); while (1) { (a = new Array(a)).sort(); } </SCRIPT> </SCRIPT> a = new Array(); while (1) { (a = new Array(a)).sort(); } </SCRIPT> </HTML> 2. Open it in firefox. Actual Results: Firefox crashed. Upon opening new firefox instance, it crashed imediatly. Upon inspecting running processes, firefox.exe was still running. This was reproduced on multiple windows xp service pack 2 machines with firefox 1.0 with the same results Expected Results: If firefox cant handle the javascript, i would expect it to timeout the script or if it had to exit, to clean up after itself.
when writing the </SCRIPT> a = new Array(); while (1) { (a = new Array(a)).sort(); } </SCRIPT> lines in the poc, remove the slash in the first <SCRIPT> tag on both lines </SCRIPT>code.......<SCRIPT> to <SCRIPT>code.......</SCRIPT> im sure you know this, just didnt want you to miss it.
Same code as attachment 167017 [details]. *** This bug has been marked as a duplicate of 271716 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.