hooglurl.blogg.se

A hostile Web page could, then, hang a user's browser simply by invoking a JavaScript infinite loop when the page loaded. The reason for this appears to be that in Firefox the same thread runs the graphical user interface and JavaScript, so while a JavaScript program is executing, menus and buttons do not work, and even window repaint does not occur. If you do click "Cancel", after another five seconds the alert pops up again ad infinitum or until the JavaScript program stops running. Note that the "OK" button cancels the execution of the script, while "Cancel" says it's OK to let the script continue. Do you want to abort the script?", accompanied by "OK" and "Cancel" buttons. If it continues to run, your computer may become unresponsive. I had no difficulty running the benchmark for five minutes in the Opera browser (which also ended up delivering the best JavaScript performance), but when I tried the same test with Mozilla Firefox, I discovered that after about five seconds, the benchmark stops and the following perversely worded alert pops up: "A script on this page is causing mozilla to run slowly. (Reported results are based on at least five runs after outliers have been discarded.) The floating point benchmark is usually run with the iteration count set so the overall benchmark runs for about five minutes that minimises start-up and end effects and averages out jitter and other inconsistencies in timing. In the process of running the recent multi-language floating point benchmarks, I wanted to time JavaScript execution in several Web browsers with (presumably) different implementations of the language. | Floating Point Benchmark: Ada 95 Benchmark Added » Friday, AugMozilla Firefox: JavaScript "Unresponsive" Timeouts and about:config « Floating Point Benchmark: Comparing Languages |