For those of you who have never encountered the most undescriptive error message Internet Explorer has to offer, it’s a doozie. No graceful javascript error, just an infinite popup with the words “stack overflow at line: 0”.
What it means: This message is an error from the javascript interpreter that probably would have crashed the browser in versions prior to 5.5.x . It is usually caused by javascript running near infinity (too much recursion possibly). The comment tag which lingers might be truncated code (if the browser stops execution, it seems strange things happen).
What caused it: It turns out our error was caused by having the following code both in the header and inline in the body:
<script type=”text/javascript” src=”tipster.js” mce_src=”tipster.js”></script>
As soon as we noticed the inline version and killed it, the issue stopped.
Microsoft has a page explaining the most common cause:
http://support.microsoft.com/default.aspx?scid=kb;en-us;816362
Some people had some luck suppressing the issue with this hack; though, I always think it is better to figure out the source than to place a bandaid:
<script type=”text/javascript”>
//<![CDATA[
self.onerror = function() { return true; }
//]]></script>
oh, and a quick shout out to twin helix, who build some incredibly useful scripts like tipster.