FIREFOX NOT RESPONDING SCRIPT HOW TO
FIREFOX NOT RESPONDING SCRIPT INSTALL
FIREFOX NOT RESPONDING SCRIPT CODE
FIREFOX NOT RESPONDING SCRIPT DOWNLOAD

FIREFOX NOT RESPONDING SCRIPT HOW TO

As to how to deal with it, I'm not a developer but surely there must be a way to stop such a runaway 'not responding' error. It can bring down the whole system to a crawl. I realise scripting uses CPU, but this crash is very serious in its nature - it's by no means 'normal' as you seem to imply. The irony is that people think that Firefox's mechanism for dealing with scripts that run for a long time is itself a problem with Firefox!!!

FIREFOX NOT RESPONDING SCRIPT CODE

Schapel wrote:In what way should Firefox 'deal' with it, in such a way that would not interfere with normal execution of JavaScript code that takes lots of memory and CPU?įirefox already does have one way of dealing with problems like these: unresponsive script warning. I'll experiment further, but it seems at least there is a repeatable way to trigger this bug that people see randomly when surfing the net. It's also randomly appeared at other websites too. If I was quick and refreshed the browser, I could reset the timer so to speak before the CPU and runaway memory leak kicked in again. I had it happen at TrekBBS when reading a long thread. This issue is by no means exclusive to CNET.

FIREFOX NOT RESPONDING SCRIPT INSTALL

I've tried a fresh profile and install of 3.5.3 - same result.īy using noscript, I can see that when scripts are permitted to run from, and com.com, the bug kicks in if you have cookies blocked. This is repeatable on three different machines running Windows XP SP3 and Avast virus/web scanner.

FIREFOX NOT RESPONDING SCRIPT DOWNLOAD

Now watch what happens in task manager when you click on the link to download - absolute chaos! For me anyway. You can also use a cookie blocker addon like cookie monster or CSlite, which does the same thing. To create this bug, simple have Javascript enabled (as default, or globally allow if using noscript) and block all cookies by using the 'tools->options->privacy menu' and clearing the tick next to 'accept cookies from sites'. I now have a completely repeatable way to trigger this bug and want to verify it first before submitting a bug report. I never had the issue, until I reinstalled without the addon NoScript, which blocks Javascript. The only way to stop this is to either refresh the page quickly, or forcably kill Firefox. I've read many people having this issue, where you'll be surfing then suddenly Firefox becomes unresponsive.Ī look in the task manager, and you'll see 100% CPU load on a single thread (eg 50% dual core) taken up by Firefox, and its memory usage sky rocketing up at an alarming rate. But now I'm positive it's a bug or an issue that needs to be prevented in the future as I can reproduce this on several machines with clean installs, so I'm posting it here.

I originally posted this in the support section, to check if it was a common issue. I've enjoyed many years of surfing and emailing with it and Thunderbird. This would at least reduce the load time of your form and would improve its performance in the browser.Hello and thanks for your support and work on this Browser. Combine those with similar 'IF' statement if necessary. However, please do understand that due to the number of your conditions, it would take some time to check them.Īlso, if possible, I suggest you reduce your conditions. Please let us know if this doesn't help so we can assist you further. You also have conditions with missing fields, please delete them as well.Īlso, some conditions are blank, please delete them.

Please don't pause them, delete them as they're not necessary. So far base on my test, the following conditions are the one causing the problem. Since you have over 170+ conditions in your form, I had to check them one by one since there's no shortcut in finding which one is buggy.

I checked your form thoroughly and base on my test, there is something in the condition that was created erroneously, it's probably looping which is the usual cause why forms are freezing in the browser.

Firefox not responding script