Closed Bug 380223 Opened 18 years ago Closed 3 years ago

Unresponsive script isn't triggered for document.write loop

Categories

(Core :: DOM: Core & HTML, defect, P3)

x86
Linux
defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: nickodell, Unassigned, NeedInfo)

References

(Depends on 1 open bug)

Details

(Keywords: regression, testcase)

Attachments

(1 file)

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20061201 Firefox/2.0.0.3 (Ubuntu-feisty) Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20061201 Firefox/2.0.0.3 (Ubuntu-feisty) <pre> <script> while (true) { document.write('<img src="hypno.gif">'); } </script> <img src="hypno.gif"> </pre> this will crash 'fox every time. Reproducible: Always Steps to Reproduce: 1.open document Actual Results: crash Expected Results: blocked the script
WFM, Firefox 2.0.0.3 on Linux (Ubuntu-edgy). I get the "Unresponsive script" warning. After clicking "Stop script" it takes several minutes before the page is rendered though. I saved the page to disk (save complete) and there were ~176000 <img> elements in it.
Does the "Quality Feedback Agent" window open when you crash? If so, please submit the crash data and let us know the incident ID. For more info: http://kb.mozillazine.org/Quality_Feedback_Agent
this is not on edgy. this problem is on feisty.
Yes, I understand you're using feisty. Please submit crash data if possible (see comment 2).
WFM, Firefox 2.0.0.4 on Ubuntu-feisty I get the "Unresponsive script" warning. After clicking "Stop script" it takes several minutes before the page is rendered, but no crash. Reporter, try starting Firefox from a command line window - do you see any error messages before it crashes?
Keywords: qawanted
Whiteboard: OOM?
Okay, I started it from the command line, but there are no error messages. It sits there, using 80% cpu, blank, unresponsive, until I close it. I could try leaving this overnight?
(In reply to comment #6) > Okay, I started it from the command line, but there are no error messages. It > sits there, using 80% cpu, blank, unresponsive, until I close it. > > I could try leaving this overnight? Not necessary. If it only hangs (not crash) then the only bug here is that you don't get the "Unresponsive script" warning dialog. Please check that the "dom.max_script_run_time" preference is set to its default value in about:config (if not, select it and click Reset on the context menu and restart Firefox and try again). Default values are displayed in a non-bold font.
Sorry I've been away. It's at default value. No error messages on command line. This doesn't even take up 1 MB of bandwidth.
I have now tested an Ubuntu build: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.3) Gecko/20061201 Firefox/2.0.0.3 (Ubuntu-feisty) I still get the same result as before: I get the "slow script" dialog, where I click "Stop script", then it takes 5 minutes or so before the page renders. Fluffy, what kind of hardware are you using?
IBM x30 thinkpad. refubished. More later... Back. Quote: "The core specification makes sense for a portable, general-purpose business machine: 1.2GHz Pentium III-M at the helm (fast enough but not so hot as a P4-M), 256MB of PC133 SDRAM memory and a 40GB hard disk."
Attached file Testcase (deleted) —
The Unresponsive script dialog opens in Firefox 2.0.0.4 for the testcase, but not in a current Firefox trunk build on Linux.
Component: File Handling → DOM
Product: Firefox → Core
QA Contact: file.handling → general
Summary: crash if javascript is enabled → Unresponsive script isn't triggered for document.write loop
Version: unspecified → Trunk
I just downloaded the latest version of Firefox. Now I'm getting the 20 second delay on loading...the "Unresponsive script" dialogue...& after selecting "Stop Script" all is running OK. Because of this delay, anything else that runs with Firefox as my main Browser will not run, ie: MS Works. Had to select IE7 as my browser until this problem is corrected. Already have tried "about:config" I filtered down to dom.max_script_run_time. I changed the default value of 20 to a higher value of 40. Problem did not go away. Can you offer more advice. Using XP with a HP Pavillion Laptop #dv6000z, Media Center edition 2006.
WELL...I deleted Firefox & then downloaded & selected the custom setup. Now, everything is running just fine. No more UNRESPONSIVE SCRIPT flags. I guess that this is the fix.
This bug looks like Bug 345161. Bug 345161 contains 2 issue. 1. document.write blocks "unresponsive script" 2. Insufficient check of "Out of memory" at document.write() causes crash. (It is now Bug 401814).
Possibly the same bug: I browse to: http://www.download.com/AVG-Anti-Virus-Free-Edition/3000-2239_4-10320142.html?tag=pop.software Doesn't make any difference how the document is retrieved (restore session, new tab and paste, or clicking through). Firefox will not crash entirely, but will display an "Unresponsive Script" warning box, but the box has no contents (it is white). Source itself does not contain document.write, but calls an external script that does contain it. I did save the source for posterity, in case it is needed.
Depends on: 1269917
Priority: -- → P3
Component: DOM → DOM: Core & HTML

(In reply to Mats Palmgren (:mats) from comment #2)

Kilitlendiğinde "Kalite Geri Bildirim Aracısı" penceresi açılıyor mu?
Öyleyse, lütfen kilitlenme verilerini gönderin ve olay kimliğini bize
bildirin.
Daha fazla bilgi için: http://kb.mozillazine.org/Quality_Feedback_Agent

Hello Jesse is this issue still available or we can close it with incomplete or worksforme?

Flags: needinfo?(jruderman)

Hello! Given that the issue hasn't been worked on in the last few years and the NI request hasn't been responded I will close this issue. If it's still available please feel free to reopen it and provide an updated testcase in order for QA to reproduce it.

Thank you!

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: