<?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: Fixing leaks</title>
	<atom:link href="http://www.squarefree.com/2007/12/27/fixing-leaks/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.squarefree.com/2007/12/27/fixing-leaks/</link>
	<description>Jesse Ruderman on Firefox, security, and more</description>
	<pubDate>Sat, 17 May 2008 19:40:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Jesse Ruderman</title>
		<link>http://www.squarefree.com/2007/12/27/fixing-leaks/#comment-4112</link>
		<dc:creator>Jesse Ruderman</dc:creator>
		<pubDate>Sat, 29 Dec 2007 01:11:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.squarefree.com/2007/12/27/fixing-leaks/#comment-4112</guid>
		<description>Hmm, &lt;a href="http://www.mozilla.org/performance/leak-tutorial.html" rel="nofollow"&gt;How to find leaks of XPCOM objects&lt;/a&gt; doesn't mention fix-macosx-stack.pl and fix-linux-stack.pl.  Those are kinda important.</description>
		<content:encoded><![CDATA[<p>Hmm, <a href="http://www.mozilla.org/performance/leak-tutorial.html" rel="nofollow">How to find leaks of XPCOM objects</a> doesn&#8217;t mention fix-macosx-stack.pl and fix-linux-stack.pl.  Those are kinda important.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse Ruderman</title>
		<link>http://www.squarefree.com/2007/12/27/fixing-leaks/#comment-4111</link>
		<dc:creator>Jesse Ruderman</dc:creator>
		<pubDate>Sat, 29 Dec 2007 01:05:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.squarefree.com/2007/12/27/fixing-leaks/#comment-4111</guid>
		<description>Using trace-refcnt summaries just to see whether you're leaking is really easy.  Just set XPCOM_MEM_LEAK_LOG to 2 and run a debug build of Firefox.  It's a great way for non-developers to find medium-sized leak bugs.

Using trace-refcnt logging to figure out &lt;i&gt;why&lt;/i&gt; you're leaking is a little tricker, but if I can figure it out, I'm sure you can, too ;) &lt;a href="http://www.mozilla.org/performance/leak-tutorial.html" rel="nofollow"&gt;How to find leaks of XPCOM objects&lt;/a&gt; is mostly about trace-refcnt and covers all the tricks Boris told me about in the bug.

I've been trying to fix up the main &lt;a href="http://wiki.mozilla.org/Performance:Leak_Tools" rel="nofollow"&gt;leak tool overview&lt;/a&gt; wiki page, but since I only barely know what I'm talking about, this is difficult ;)</description>
		<content:encoded><![CDATA[<p>Using trace-refcnt summaries just to see whether you&#8217;re leaking is really easy.  Just set XPCOM_MEM_LEAK_LOG to 2 and run a debug build of Firefox.  It&#8217;s a great way for non-developers to find medium-sized leak bugs.</p>
<p>Using trace-refcnt logging to figure out <i>why</i> you&#8217;re leaking is a little tricker, but if I can figure it out, I&#8217;m sure you can, too ;) <a href="http://www.mozilla.org/performance/leak-tutorial.html" rel="nofollow">How to find leaks of XPCOM objects</a> is mostly about trace-refcnt and covers all the tricks Boris told me about in the bug.</p>
<p>I&#8217;ve been trying to fix up the main <a href="http://wiki.mozilla.org/Performance:Leak_Tools" rel="nofollow">leak tool overview</a> wiki page, but since I only barely know what I&#8217;m talking about, this is difficult ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VanillaMozilla</title>
		<link>http://www.squarefree.com/2007/12/27/fixing-leaks/#comment-4110</link>
		<dc:creator>VanillaMozilla</dc:creator>
		<pubDate>Fri, 28 Dec 2007 15:39:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.squarefree.com/2007/12/27/fixing-leaks/#comment-4110</guid>
		<description>Unfortunately, based on my experience, bugs that no one else can reproduce seem to be fairly common.  This can happen even with a new profile, and unlike this case, usually the cause is never found.

There are also problems with user support and standard bug reporting procedures, at least as far as the public is told.  The public is discouraged from reporting bugs when used with themes and extensions.  The addon is almost always blamed unless someone tracks the problem down from inside the code.

It still seems like each new release breaks something.  I don't know what to suggest.  I just think it's worth pointing out.  This stuff is so complicated and poorly understood that I sometimes wonder why it works at all.</description>
		<content:encoded><![CDATA[<p>Unfortunately, based on my experience, bugs that no one else can reproduce seem to be fairly common.  This can happen even with a new profile, and unlike this case, usually the cause is never found.</p>
<p>There are also problems with user support and standard bug reporting procedures, at least as far as the public is told.  The public is discouraged from reporting bugs when used with themes and extensions.  The addon is almost always blamed unless someone tracks the problem down from inside the code.</p>
<p>It still seems like each new release breaks something.  I don&#8217;t know what to suggest.  I just think it&#8217;s worth pointing out.  This stuff is so complicated and poorly understood that I sometimes wonder why it works at all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Håkan W</title>
		<link>http://www.squarefree.com/2007/12/27/fixing-leaks/#comment-4109</link>
		<dc:creator>Håkan W</dc:creator>
		<pubDate>Fri, 28 Dec 2007 14:03:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.squarefree.com/2007/12/27/fixing-leaks/#comment-4109</guid>
		<description>It would be awesome if you'd document the stuff you learned from Boris and Jonas somewhere. Is using tracerefcnt hard? Are there any good docs out there on this?</description>
		<content:encoded><![CDATA[<p>It would be awesome if you&#8217;d document the stuff you learned from Boris and Jonas somewhere. Is using tracerefcnt hard? Are there any good docs out there on this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pd</title>
		<link>http://www.squarefree.com/2007/12/27/fixing-leaks/#comment-4108</link>
		<dc:creator>pd</dc:creator>
		<pubDate>Fri, 28 Dec 2007 10:19:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.squarefree.com/2007/12/27/fixing-leaks/#comment-4108</guid>
		<description>Jesse you're a complete legend.

Thanks for this excellent work. Unfortunately it's largely invisible to the user however that does not mean it is less meaningful than a UI tweak. It is more so. Personally I really enjoy reading posts that point out the normally invisible fixes that will make such a difference.

Thanks again</description>
		<content:encoded><![CDATA[<p>Jesse you&#8217;re a complete legend.</p>
<p>Thanks for this excellent work. Unfortunately it&#8217;s largely invisible to the user however that does not mean it is less meaningful than a UI tweak. It is more so. Personally I really enjoy reading posts that point out the normally invisible fixes that will make such a difference.</p>
<p>Thanks again</p>
]]></content:encoded>
	</item>
</channel>
</rss>
