<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Possible Memory Issue with NoScript 1.4.9.5?</title>
	<atom:link href="http://www.computerdefense.org/2008/03/possible-memory-issue-with-noscript-1495/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.computerdefense.org/2008/03/possible-memory-issue-with-noscript-1495/</link>
	<description>Sharing my thoughts with the world.</description>
	<lastBuildDate>Wed, 16 Nov 2011 02:58:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: kurt wismer</title>
		<link>http://www.computerdefense.org/2008/03/possible-memory-issue-with-noscript-1495/comment-page-1/#comment-77530</link>
		<dc:creator>kurt wismer</dc:creator>
		<pubDate>Tue, 20 Jan 2009 09:10:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.computerdefense.org/2008/03/09/possible-memory-issue-with-noscript-1495/#comment-77530</guid>
		<description>i use firefox and noscript - my observations are as follows: &lt;br /&gt;
- firefox doesn&#039;t use 450MB when it starts (more like 100), but it can certainly grow to that size over time... &lt;br /&gt;
- i never let it get that far - at 250-300MB (the point at which i generally start encountering script timeouts) i kill the process and start it again... &lt;br /&gt;
- i haven&#039;t noticed any recent changes in this behaviour... </description>
		<content:encoded><![CDATA[<p>i use firefox and noscript &#8211; my observations are as follows: <br />
- firefox doesn&#039;t use 450MB when it starts (more like 100), but it can certainly grow to that size over time&#8230; <br />
- i never let it get that far &#8211; at 250-300MB (the point at which i generally start encountering script timeouts) i kill the process and start it again&#8230; <br />
- i haven&#039;t noticed any recent changes in this behaviour&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tyler_regul5659</title>
		<link>http://www.computerdefense.org/2008/03/possible-memory-issue-with-noscript-1495/comment-page-1/#comment-77386</link>
		<dc:creator>tyler_regul5659</dc:creator>
		<pubDate>Mon, 19 Jan 2009 14:20:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.computerdefense.org/2008/03/09/possible-memory-issue-with-noscript-1495/#comment-77386</guid>
		<description>I&#039;ve never really experienced script timeouts, however I will run firefox for days at a time, and I do use a number of plugins. For example, the machine in the original post is Vista... on this XP box, Firefox (after 3 hours) is at 250MB. I currently have 7 tabs open. I&#039;ve never been over 450 before, except with the last NoScript and that went away as soon as I disabled it.  </description>
		<content:encoded><![CDATA[<p>I&#039;ve never really experienced script timeouts, however I will run firefox for days at a time, and I do use a number of plugins. For example, the machine in the original post is Vista&#8230; on this XP box, Firefox (after 3 hours) is at 250MB. I currently have 7 tabs open. I&#039;ve never been over 450 before, except with the last NoScript and that went away as soon as I disabled it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

