<?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: Firefox memory leak progress</title>
	<atom:link href="http://www.squarefree.com/2006/02/04/memory-leak-progress/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.squarefree.com/2006/02/04/memory-leak-progress/</link>
	<description>Jesse Ruderman on Firefox, security, and more</description>
	<pubDate>Fri, 25 Jul 2008 16:51:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: firefox &#187; Firefox内存泄露的进展</title>
		<link>http://www.squarefree.com/2006/02/04/memory-leak-progress/#comment-2103</link>
		<dc:creator>firefox &#187; Firefox内存泄露的进展</dc:creator>
		<pubDate>Fri, 03 Mar 2006 09:34:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.squarefree.com/2006/02/04/memory-leak-progress/#comment-2103</guid>
		<description>[...] 这篇文章（作者是开发者）解释了目前这个问题的进展，首先是可以用最新版，稳定版是1.5.0.1，刚出的，它比1.5修复了两个泄露的地方；其次是如果想进一步研究，可以用一些工具来（Perl和Javascript的）分析log文件，从而获取是哪些东西泄露了。 [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] 这篇文章（作者是开发者）解释了目前这个问题的进展，首先是可以用最新版，稳定版是1.5.0.1，刚出的，它比1.5修复了两个泄露的地方；其次是如果想进一步研究，可以用一些工具来（Perl和Javascript的）分析log文件，从而获取是哪些东西泄露了。 [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: firefox &#187; 如何减少 firefox 的内存使用</title>
		<link>http://www.squarefree.com/2006/02/04/memory-leak-progress/#comment-2102</link>
		<dc:creator>firefox &#187; 如何减少 firefox 的内存使用</dc:creator>
		<pubDate>Fri, 03 Mar 2006 09:30:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.squarefree.com/2006/02/04/memory-leak-progress/#comment-2102</guid>
		<description>[...] 内存泄漏参考这两篇文章 http://www.squarefree.com/2006/02/04/memory-leak-progress/ http://www.squarefree.com/2006/01/13/memory-leak-detection-tool/ [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] 内存泄漏参考这两篇文章 <a href="http://www.squarefree.com/2006/02/04/memory-leak-progress/" rel="nofollow">http://www.squarefree.com/2006/02/04/memory-leak-progress/</a> <a href="http://www.squarefree.com/2006/01/13/memory-leak-detection-tool/" rel="nofollow">http://www.squarefree.com/2006/01/13/memory-leak-detection-tool/</a> [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: No hay rosa sin espina &#187; Memory leaks en Firefox</title>
		<link>http://www.squarefree.com/2006/02/04/memory-leak-progress/#comment-2098</link>
		<dc:creator>No hay rosa sin espina &#187; Memory leaks en Firefox</dc:creator>
		<pubDate>Tue, 28 Feb 2006 01:11:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.squarefree.com/2006/02/04/memory-leak-progress/#comment-2098</guid>
		<description>[...] En las últimas versiones los ingenieros del proyecto han trabajado duro para eliminar todas esas &#8220;fugas&#8221; de memoria (los famosos memory leaks) reportadas pero todavía queda un largo camino. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] En las últimas versiones los ingenieros del proyecto han trabajado duro para eliminar todas esas &#8220;fugas&#8221; de memoria (los famosos memory leaks) reportadas pero todavía queda un largo camino. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: steve england</title>
		<link>http://www.squarefree.com/2006/02/04/memory-leak-progress/#comment-2097</link>
		<dc:creator>steve england</dc:creator>
		<pubDate>Mon, 27 Feb 2006 18:15:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.squarefree.com/2006/02/04/memory-leak-progress/#comment-2097</guid>
		<description>[quote]Menu X causes a big leak in combo with Groowe and/or Clusty.[/quote]

Not for me. Tested with leak-gauge.pl and no reported leaks with all three extensions installed.</description>
		<content:encoded><![CDATA[<p>[quote]Menu X causes a big leak in combo with Groowe and/or Clusty.[/quote]</p>
<p>Not for me. Tested with leak-gauge.pl and no reported leaks with all three extensions installed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Curtis dot Org: Random Musings of Chris Curtis and Co.</title>
		<link>http://www.squarefree.com/2006/02/04/memory-leak-progress/#comment-2076</link>
		<dc:creator>Chris Curtis dot Org: Random Musings of Chris Curtis and Co.</dc:creator>
		<pubDate>Sat, 18 Feb 2006 01:28:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.squarefree.com/2006/02/04/memory-leak-progress/#comment-2076</guid>
		<description>[...] So, minimizing the amount of memory that Firefox uses is obviously something I&#8217;d be interested in.&#160; A Wired.com &#8220;monkey bite&#8221; led me to this mozillazine entry discussing (both real and not) &#8220;memory leaks&#8221; in the application.&#160; That, in turn, led me to a more useful article by Jesse Ruderman (who I gather is a contributor to Mozilla) on memory leak progress in Firefox (and the trunk builds).&#160; Of course, Jesse&#8217;s entry itself led me to a detection tool for leaks as well as a general memory usage info thread and reducing memory usage information. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] So, minimizing the amount of memory that Firefox uses is obviously something I&#8217;d be interested in.&nbsp; A Wired.com &#8220;monkey bite&#8221; led me to this mozillazine entry discussing (both real and not) &#8220;memory leaks&#8221; in the application.&nbsp; That, in turn, led me to a more useful article by Jesse Ruderman (who I gather is a contributor to Mozilla) on memory leak progress in Firefox (and the trunk builds).&nbsp; Of course, Jesse&#8217;s entry itself led me to a detection tool for leaks as well as a general memory usage info thread and reducing memory usage information. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Krissa</title>
		<link>http://www.squarefree.com/2006/02/04/memory-leak-progress/#comment-2071</link>
		<dc:creator>Krissa</dc:creator>
		<pubDate>Wed, 15 Feb 2006 02:40:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.squarefree.com/2006/02/04/memory-leak-progress/#comment-2071</guid>
		<description>Menu X causes a big leak in combo with Groowe and/or Clusty.</description>
		<content:encoded><![CDATA[<p>Menu X causes a big leak in combo with Groowe and/or Clusty.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
