<?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: Back to the 1.8 branch, part 2?</title>
	<atom:link href="http://blog.dolphinling.net/2006/06/back-to-the-18-branch-part-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.dolphinling.net/2006/06/back-to-the-18-branch-part-2/</link>
	<description>...whatever goes through my head...</description>
	<lastBuildDate>Fri, 22 Jan 2010 11:50:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Martijn</title>
		<link>http://blog.dolphinling.net/2006/06/back-to-the-18-branch-part-2/comment-page-1/#comment-2031</link>
		<dc:creator>Martijn</dc:creator>
		<pubDate>Fri, 30 Jun 2006 02:07:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dolphinling.net/2006/06/back-to-the-18-branch-part-2/#comment-2031</guid>
		<description>Well, the bug I mentioned is blocking/related to https://bugzilla.mozilla.org/show_bug.cgi?id=340260 which isn&#039;t about GMail at all.
That bug describes memory issues for Seamonkey and Thunderbird.
Maybe you&#039;re seeing the same regression range for the memory issues you&#039;re having? That might be worth investigating.</description>
		<content:encoded><![CDATA[<p>Well, the bug I mentioned is blocking/related to <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=340260" rel="nofollow">https://bugzilla.mozilla.org/show_bug.cgi?id=340260</a> which isn&#8217;t about GMail at all.<br />
That bug describes memory issues for Seamonkey and Thunderbird.<br />
Maybe you&#8217;re seeing the same regression range for the memory issues you&#8217;re having? That might be worth investigating.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dolphinling</title>
		<link>http://blog.dolphinling.net/2006/06/back-to-the-18-branch-part-2/comment-page-1/#comment-2028</link>
		<dc:creator>dolphinling</dc:creator>
		<pubDate>Thu, 29 Jun 2006 15:02:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dolphinling.net/2006/06/back-to-the-18-branch-part-2/#comment-2028</guid>
		<description>&lt;p&gt;Perhaps if I used gmail it might be. ;)&lt;/p&gt;&lt;p&gt;Actually, my current thinking is that there are three (or more): one that&#039;s an extension problem (linky, perhaps?) that&#039;s the bulk of what I&#039;m seeing, one that I&#039;ve filed as &lt;a href=&quot;https://bugzilla.mozilla.org/show_bug.cgi?id=342802&quot; rel=&quot;nofollow&quot;&gt;Bug 342802&lt;/a&gt; that was messing up my testing (because I&#039;d see a huge leak early on, and think &quot;Oh, that must correspond to my giant leak in normal usage!&quot;), and a few more small ones that make it so I can&#039;t just open the browser for a few moments, check leak-gauge.pl and see if anything leaked, I have to actually leave it open for a long time and use it to see if the leak was big.&lt;/p&gt;
&lt;p&gt;So yeah. I don&#039;t feel like spending a few hours testing each extension, so maybe when I feel more motivated I&#039;ll look into it again, or maybe it&#039;ll just fix itself if someone else sees it.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Perhaps if I used gmail it might be. ;)</p>
<p>Actually, my current thinking is that there are three (or more): one that&#8217;s an extension problem (linky, perhaps?) that&#8217;s the bulk of what I&#8217;m seeing, one that I&#8217;ve filed as <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=342802" rel="nofollow">Bug 342802</a> that was messing up my testing (because I&#8217;d see a huge leak early on, and think &#8220;Oh, that must correspond to my giant leak in normal usage!&#8221;), and a few more small ones that make it so I can&#8217;t just open the browser for a few moments, check leak-gauge.pl and see if anything leaked, I have to actually leave it open for a long time and use it to see if the leak was big.</p>
<p>So yeah. I don&#8217;t feel like spending a few hours testing each extension, so maybe when I feel more motivated I&#8217;ll look into it again, or maybe it&#8217;ll just fix itself if someone else sees it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martijn</title>
		<link>http://blog.dolphinling.net/2006/06/back-to-the-18-branch-part-2/comment-page-1/#comment-2027</link>
		<dc:creator>Martijn</dc:creator>
		<pubDate>Thu, 29 Jun 2006 13:39:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.dolphinling.net/2006/06/back-to-the-18-branch-part-2/#comment-2027</guid>
		<description>Maybe the memory leak you are seeing is https://bugzilla.mozilla.org/show_bug.cgi?id=341430 (and dependant bug)?</description>
		<content:encoded><![CDATA[<p>Maybe the memory leak you are seeing is <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=341430" rel="nofollow">https://bugzilla.mozilla.org/show_bug.cgi?id=341430</a> (and dependant bug)?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
