<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Safari crashing</title>
	<atom:link href="http://www.nnyman.com/personal/2006/08/08/safari-crashing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.nnyman.com/personal/2006/08/08/safari-crashing/</link>
	<description>Niko Nyman's blog on shifting topics.</description>
	<pubDate>Mon, 01 Dec 2008 17:42:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Niko</title>
		<link>http://www.nnyman.com/personal/2006/08/08/safari-crashing/#comment-2915</link>
		<dc:creator>Niko</dc:creator>
		<pubDate>Tue, 15 Aug 2006 18:41:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.nnyman.com/personal/2006/08/08/safari-crashing/#comment-2915</guid>
		<description>&lt;p&gt;Mine has worked fine after doing the magic permissions thing. And I'm totally keeping my hands off DOMs and trees. ;)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Mine has worked fine after doing the magic permissions thing. And I&#8217;m totally keeping my hands off DOMs and trees. ;)</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Markku</title>
		<link>http://www.nnyman.com/personal/2006/08/08/safari-crashing/#comment-2855</link>
		<dc:creator>Markku</dc:creator>
		<pubDate>Sun, 13 Aug 2006 19:22:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.nnyman.com/personal/2006/08/08/safari-crashing/#comment-2855</guid>
		<description>&lt;p&gt;Just figured it out after a couple of days of playing around.. apparently if you launch a script from inside an element which hides the element using display='none', Safari's DOM tree is somehow messed up and you cannot no longer access the hidden element's parentNode or anything above it. The situation becomes a "memory violation", which shouldn't happen of course.&lt;/p&gt;

&lt;p&gt;This was the situation for me, there seems to be a lot of unsolved Safari bugs around which crash the browser without any warning.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Just figured it out after a couple of days of playing around.. apparently if you launch a script from inside an element which hides the element using display=&#8217;none&#8217;, Safari&#8217;s DOM tree is somehow messed up and you cannot no longer access the hidden element&#8217;s parentNode or anything above it. The situation becomes a &#8220;memory violation&#8221;, which shouldn&#8217;t happen of course.</p>

<p>This was the situation for me, there seems to be a lot of unsolved Safari bugs around which crash the browser without any warning.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Pascal</title>
		<link>http://www.nnyman.com/personal/2006/08/08/safari-crashing/#comment-2823</link>
		<dc:creator>Pascal</dc:creator>
		<pubDate>Sat, 12 Aug 2006 17:53:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.nnyman.com/personal/2006/08/08/safari-crashing/#comment-2823</guid>
		<description>&lt;p&gt;I have run into crashes myself, and while I wouldn't be surprised if it turns out to be related to modifying the DOM tree, trashing the preference file has worked wonders for me every single time.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I have run into crashes myself, and while I wouldn&#8217;t be surprised if it turns out to be related to modifying the DOM tree, trashing the preference file has worked wonders for me every single time.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Markku</title>
		<link>http://www.nnyman.com/personal/2006/08/08/safari-crashing/#comment-2715</link>
		<dc:creator>Markku</dc:creator>
		<pubDate>Wed, 09 Aug 2006 08:24:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.nnyman.com/personal/2006/08/08/safari-crashing/#comment-2715</guid>
		<description>&lt;p&gt;Same here.. Mine started crashing particularly on some web2.0 sites, for example when using netvibes.com or other javascript heavy services.&lt;/p&gt;

&lt;p&gt;I first noticed the thing as I'm working on a RoR project with a javascripted UI, and Safari keeps crashing all the time on it. This problem at least has something to do with modifying the DOM tree on the fly, which Safari doesn't seem to like in every situation. Firefox/IE has no problems with it and the code has been checked a thousand times... Very annoying.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Same here.. Mine started crashing particularly on some web2.0 sites, for example when using netvibes.com or other javascript heavy services.</p>

<p>I first noticed the thing as I&#8217;m working on a RoR project with a javascripted UI, and Safari keeps crashing all the time on it. This problem at least has something to do with modifying the DOM tree on the fly, which Safari doesn&#8217;t seem to like in every situation. Firefox/IE has no problems with it and the code has been checked a thousand times&#8230; Very annoying.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Niko</title>
		<link>http://www.nnyman.com/personal/2006/08/08/safari-crashing/#comment-2697</link>
		<dc:creator>Niko</dc:creator>
		<pubDate>Tue, 08 Aug 2006 18:52:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.nnyman.com/personal/2006/08/08/safari-crashing/#comment-2697</guid>
		<description>&lt;p&gt;I tried manually repairing permissions and running the daily/weekly/monthly scripts. Let's see if that helps.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I tried manually repairing permissions and running the daily/weekly/monthly scripts. Let&#8217;s see if that helps.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Petri</title>
		<link>http://www.nnyman.com/personal/2006/08/08/safari-crashing/#comment-2696</link>
		<dc:creator>Petri</dc:creator>
		<pubDate>Tue, 08 Aug 2006 18:32:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.nnyman.com/personal/2006/08/08/safari-crashing/#comment-2696</guid>
		<description>&lt;p&gt;I noticed the same thing. &lt;a href="http://www.macupdate.com/info.php/id/7076" title="System Optimizer X on MacUpdate"&gt;System Optimizer X&lt;/a&gt; solved the problem, but mine could've been different from yours...&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I noticed the same thing. <a href="http://www.macupdate.com/info.php/id/7076" title="System Optimizer X on MacUpdate">System Optimizer X</a> solved the problem, but mine could&#8217;ve been different from yours&#8230;</p>]]></content:encoded>
	</item>
</channel>
</rss>
