Closed Bug 392219 Opened 17 years ago Closed 17 years ago

freeze up with javascript loop and window.open()

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 379151

People

(Reporter: jmg728, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6 Firefox will freeze and be unresponsive if a web page has a infinite loop along with multiple window.open("loop_exploit.htm") statements, where loop_exploit.htm is the filename of the web page containing the script. Please note that you must have multiple statements. In the example, 9 window.open("loop_exploit.htm") statements were included. Reproducible: Always Steps to Reproduce: WARNING: this will render Firefox UNRESPONSIVE and you will need to manually end its PROCESS through use of the task manager to close Fx. 1. Open a text editor and paste the following HTML code: <html> <body> <script type="text/javascript"> while(1<2){ window.open("loop_exploit.htm"); window.open("loop_exploit.htm"); window.open("loop_exploit.htm"); window.open("loop_exploit.htm"); window.open("loop_exploit.htm"); window.open("loop_exploit.htm"); window.open("loop_exploit.htm"); window.open("loop_exploit.htm"); window.open("loop_exploit.htm"); } </script> </body> </html> 2. Open the web page in Firefox. Actual Results: Firefox quickly becomes unresponsive and memory usage rises very fast. On my computer, Firefox rose from about 40000K of mem. usage to about 100000K in about 30 seconds. Expected Results: Firefox should have displayed the normal statement that it gives when a javascript script is taking longer than usual to execute instead of freezing. I was using WinXP, Intel Pentium 4 HT (3.00GHz), 1GB RAM.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.