Some webpages frenquently call JavaScript functions that cause errors. For example, if a function is called onMouseMove and this function uses MSIE-specific code (like in the given page), this may use a lot of free memory, slowing down other programs. If there would be a limit on the JS errors one page can produce, this problem would be solved. Say, when the page has produced more than 20 errors, no more JavaScript is executed for that page and an error message is shown.

If you run mozilla with -console and view the link http://www.hpichina.org/asp/index.htm you will see the following error repeaded over and over: JavaScript error: http://www.hpichina.org/asp/index.htm line 9: window.event has no properties I orignally showed cheezy and others in #mozillazine this page. My question was were we doing everything correct on the Mozilla side. If we are doing things right is this error slowing things down. If it is a MS IE/Frontpage thing like many think it could be is the problem common. The question was did the error condition slow things down.

I am also expirencing a large amount of these errors, which eventually leads to a crash. Linux 2000062108 Viewing http://www.playnow.com.au/features/e3_00/content/valve_borg/index2.asp results in many javascript window.event errors. See output from terminal below: Document http://www.playnow.com.au/features/e3_00/content/valve_borg/index2.asp loaded successfully JavaScript error: http://www.playnow.com.au/features/e3_00/content/valve_borg/index2.asp line 277: window.event has no properties JavaScript error: http://www.playnow.com.au/features/e3_00/content/valve_borg/index2.asp line 283: window.event has no properties JavaScript error: http://www.playnow.com.au/features/e3_00/content/valve_borg/index2.asp line 277: window.event has no properties JavaScript error: http://www.playnow.com.au/features/e3_00/content/valve_borg/index2.asp line 283: window.event has no properties JavaScript error: http://www.playnow.com.au/features/e3_00/content/valve_borg/index2.asp line 277: window.event has no properties JavaScript error: http://www.playnow.com.au/features/e3_00/content/valve_borg/index2.asp line 283: window.event has no properties ./run-mozilla.sh: line 29: 1768 Segmentation fault $prog ${1+"$@"}

Embedding issue, not engine. Reassigning to Browser-General for disposition -

over to DOM for evaluation.

This bug has been marked "future" because the original netscape engineer working on this is over-burdened. If you feel this is an error, that you or another known resource will be working on this bug, or if it blocks your work in some way -- please attach your concern to the bug for reconsideration.

Not sure who fixed this but there is a limit on the number of errors in the current JS console and I'm not able to reproduce a crash when mousing around on that page for quite some time (I do see the console filling up to the limit but that's where it stops). Marking FIXED.