<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:series="http://unfoldingneurons.com/"
	>

<channel>
	<title>The Shane &#038; Peter Inc. Blog &#187; Javascript</title>
	<atom:link href="http://blog.shaneandpeter.com/category/technology/javascript/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.shaneandpeter.com</link>
	<description>Bridging People &#038; Technology</description>
	<lastBuildDate>Fri, 20 Aug 2010 00:09:50 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>stack overflow at line: 0</title>
		<link>http://blog.shaneandpeter.com/2007/06/12/internet-explorer-javascript-error-stack-overflow-at-line-0/</link>
		<comments>http://blog.shaneandpeter.com/2007/06/12/internet-explorer-javascript-error-stack-overflow-at-line-0/#comments</comments>
		<pubDate>Wed, 13 Jun 2007 01:21:13 +0000</pubDate>
		<dc:creator>shane</dc:creator>
				<category><![CDATA[Browser]]></category>
		<category><![CDATA[Javascript]]></category>
		<category><![CDATA[The Technicals]]></category>

		<guid isPermaLink="false">http://blog.shaneandpeter.com/2007/06/12/internet-explorer-javascript-error-stack-overflow-at-line-0/</guid>
		<description><![CDATA[For those of you who have never encountered the most undescriptive error message Internet Explorer has to offer, it&#8217;s a doozie. No graceful javascript error, just an infinite popup with the words &#8220;stack overflow at line: 0&#8243;.
What it means: This message is an error from the javascript interpreter that probably would have crashed the browser [...]]]></description>
			<content:encoded><![CDATA[<p>For those of you who have never encountered the most undescriptive error message Internet Explorer has to offer, it&#8217;s a doozie. No graceful javascript error, just an infinite popup with the words &#8220;stack overflow at line: 0&#8243;.</p>
<p><strong>What it means: </strong>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).</p>
<p><strong>What caused it:</strong> It turns out our error was caused by having the following code both in the header and inline in the body:</p>
<p>&lt;script type=&#8221;text/javascript&#8221; src=&#8221;tipster.js&#8221; mce_src=&#8221;tipster.js&#8221;&gt;&lt;/script&gt;</p>
<p>As soon as we noticed the inline version and killed it, the issue stopped.</p>
<p>Microsoft has a page explaining the most common cause:</p>
<p><a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;816362">http://support.microsoft.com/default.aspx?scid=kb;en-us;816362</a></p>
<p>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:</p>
<p>&lt;script type=&#8221;text/javascript&#8221;&gt;<br />
//&lt;![CDATA[<br />
self.onerror = function() { return true; }<br />
//]]&gt;&lt;/script&gt;</p>
<p>oh, and a quick shout out to <a target="_blank" href="http://www.twinhelix.com/">twin helix</a>, who build some incredibly useful scripts like <a target="_blank" href="http://www.twinhelix.com/dhtml/tipster/">tipster</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.shaneandpeter.com/2007/06/12/internet-explorer-javascript-error-stack-overflow-at-line-0/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
