<?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: Testing extensions for memory leaks on Trunk.</title>
	<atom:link href="http://steveengland.wordpress.com/2007/07/18/testing-extensions-for-memory-leaks-on-trunk/feed/" rel="self" type="application/rss+xml" />
	<link>http://steveengland.wordpress.com/2007/07/18/testing-extensions-for-memory-leaks-on-trunk/</link>
	<description>Like the world needed another</description>
	<pubDate>Wed, 09 Jul 2008 13:03:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
		<item>
		<title>By: Get Firefox Now &#187; Firefox Memory Leaks.</title>
		<link>http://steveengland.wordpress.com/2007/07/18/testing-extensions-for-memory-leaks-on-trunk/#comment-348</link>
		<dc:creator>Get Firefox Now &#187; Firefox Memory Leaks.</dc:creator>
		<pubDate>Fri, 19 Oct 2007 17:02:51 +0000</pubDate>
		<guid isPermaLink="false">http://steveengland.wordpress.com/2007/07/18/testing-extensions-for-memory-leaks-on-trunk/#comment-348</guid>
		<description>[...] England tested the top 500 web sites, finding two leaks. Later, he tested the top 20 Firefox extensions and found leaks in several of [...]</description>
		<content:encoded><![CDATA[<p>[...] England tested the top 500 web sites, finding two leaks. Later, he tested the top 20 Firefox extensions and found leaks in several of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: links for 2007-10-16 &#171; Mandarine</title>
		<link>http://steveengland.wordpress.com/2007/07/18/testing-extensions-for-memory-leaks-on-trunk/#comment-335</link>
		<dc:creator>links for 2007-10-16 &#171; Mandarine</dc:creator>
		<pubDate>Tue, 16 Oct 2007 04:26:11 +0000</pubDate>
		<guid isPermaLink="false">http://steveengland.wordpress.com/2007/07/18/testing-extensions-for-memory-leaks-on-trunk/#comment-335</guid>
		<description>[...] Testing extensions for memory leaks on Trunk Thusly, my scope for these tests was quite small; I individually tested the top 20 extensions listed on AMO plus a few of the extensions that I personally use. (tags: firefox extensions) [...]</description>
		<content:encoded><![CDATA[<p>[...] Testing extensions for memory leaks on Trunk Thusly, my scope for these tests was quite small; I individually tested the top 20 extensions listed on AMO plus a few of the extensions that I personally use. (tags: firefox extensions) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve England</title>
		<link>http://steveengland.wordpress.com/2007/07/18/testing-extensions-for-memory-leaks-on-trunk/#comment-268</link>
		<dc:creator>Steve England</dc:creator>
		<pubDate>Thu, 27 Sep 2007 11:11:38 +0000</pubDate>
		<guid isPermaLink="false">http://steveengland.wordpress.com/2007/07/18/testing-extensions-for-memory-leaks-on-trunk/#comment-268</guid>
		<description>Hi Jonah. I'm not sure how much I can expand on what I already wrote about how I tested the extensions: "I installed one extension at a time and then tried using it, setting different options and generally screw around on firefox for a while. Then firefox would get closed and the nspr.log analysed for leakage."

I basically tried to use the extension for what it was intended (downloading videos, say, or removing page elements, or whatever). There was no scientific approach to the test, just one guy trying various extensions and seeing if he could catch a leak somehow.</description>
		<content:encoded><![CDATA[<p>Hi Jonah. I&#8217;m not sure how much I can expand on what I already wrote about how I tested the extensions: &#8220;I installed one extension at a time and then tried using it, setting different options and generally screw around on firefox for a while. Then firefox would get closed and the nspr.log analysed for leakage.&#8221;</p>
<p>I basically tried to use the extension for what it was intended (downloading videos, say, or removing page elements, or whatever). There was no scientific approach to the test, just one guy trying various extensions and seeing if he could catch a leak somehow.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonah Bishop</title>
		<link>http://steveengland.wordpress.com/2007/07/18/testing-extensions-for-memory-leaks-on-trunk/#comment-256</link>
		<dc:creator>Jonah Bishop</dc:creator>
		<pubDate>Mon, 24 Sep 2007 16:49:24 +0000</pubDate>
		<guid isPermaLink="false">http://steveengland.wordpress.com/2007/07/18/testing-extensions-for-memory-leaks-on-trunk/#comment-256</guid>
		<description>Can you shed some light on *how* you tested these extensions? For example, what was the setup process you went through? I've got a couple of extensions that I've written, and I'd like to check them for leaks just to make sure I'm doing things the right way. Thanks in advance!</description>
		<content:encoded><![CDATA[<p>Can you shed some light on *how* you tested these extensions? For example, what was the setup process you went through? I&#8217;ve got a couple of extensions that I&#8217;ve written, and I&#8217;d like to check them for leaks just to make sure I&#8217;m doing things the right way. Thanks in advance!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alanjstr</title>
		<link>http://steveengland.wordpress.com/2007/07/18/testing-extensions-for-memory-leaks-on-trunk/#comment-251</link>
		<dc:creator>alanjstr</dc:creator>
		<pubDate>Sat, 22 Sep 2007 16:07:21 +0000</pubDate>
		<guid isPermaLink="false">http://steveengland.wordpress.com/2007/07/18/testing-extensions-for-memory-leaks-on-trunk/#comment-251</guid>
		<description>Its great that you've been testing addons.  If you blog about Mozilla stuff often, maybe you should get listed on http://gemal.dk/mozilla/blogupdates.html .  That's where I go for my news summary.</description>
		<content:encoded><![CDATA[<p>Its great that you&#8217;ve been testing addons.  If you blog about Mozilla stuff often, maybe you should get listed on <a href="http://gemal.dk/mozilla/blogupdates.html" rel="nofollow">http://gemal.dk/mozilla/blogupdates.html</a> .  That&#8217;s where I go for my news summary.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve England</title>
		<link>http://steveengland.wordpress.com/2007/07/18/testing-extensions-for-memory-leaks-on-trunk/#comment-249</link>
		<dc:creator>Steve England</dc:creator>
		<pubDate>Sat, 22 Sep 2007 10:39:47 +0000</pubDate>
		<guid isPermaLink="false">http://steveengland.wordpress.com/2007/07/18/testing-extensions-for-memory-leaks-on-trunk/#comment-249</guid>
		<description>Thanks for the feedback Gérard! I'll look at the other default themes and see if there's something more usable.</description>
		<content:encoded><![CDATA[<p>Thanks for the feedback Gérard! I&#8217;ll look at the other default themes and see if there&#8217;s something more usable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Luz</title>
		<link>http://steveengland.wordpress.com/2007/07/18/testing-extensions-for-memory-leaks-on-trunk/#comment-242</link>
		<dc:creator>Daniel Luz</dc:creator>
		<pubDate>Fri, 21 Sep 2007 01:07:28 +0000</pubDate>
		<guid isPermaLink="false">http://steveengland.wordpress.com/2007/07/18/testing-extensions-for-memory-leaks-on-trunk/#comment-242</guid>
		<description>Oh, I only learned of this post today, on Jesse Ruderman's blog…

That's too bad about AIO, I'll see if I can find anything (that if it still leaks on Minefield). It seems somebody else also found it to be leaking, so at least I'm not seeing illusions :) https://addons.mozilla.org/en-US/firefox/discussions/comments.php?DiscussionID=3907&#38;page=1#Item_0</description>
		<content:encoded><![CDATA[<p>Oh, I only learned of this post today, on Jesse Ruderman&#8217;s blog…</p>
<p>That&#8217;s too bad about AIO, I&#8217;ll see if I can find anything (that if it still leaks on Minefield). It seems somebody else also found it to be leaking, so at least I&#8217;m not seeing illusions :) <a href="https://addons.mozilla.org/en-US/firefox/discussions/comments.php?DiscussionID=3907&amp;page=1#Item_0" rel="nofollow">https://addons.mozilla.org/en-US/firefox/discussions/comments.php?DiscussionID=3907&amp;page=1#Item_0</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gérard Talbot</title>
		<link>http://steveengland.wordpress.com/2007/07/18/testing-extensions-for-memory-leaks-on-trunk/#comment-241</link>
		<dc:creator>Gérard Talbot</dc:creator>
		<pubDate>Thu, 20 Sep 2007 23:28:58 +0000</pubDate>
		<guid isPermaLink="false">http://steveengland.wordpress.com/2007/07/18/testing-extensions-for-memory-leaks-on-trunk/#comment-241</guid>
		<description>Ian, the keywords like mlk can be added to a mozdev bug report, but only the reporter or assignee.

Add to the list of resolved memory leakage bug reports at mozdev for Firefox add-on extensions (but without a mlk keyword):

FlashBlock 1.5.1
https://www.mozdev.org/bugs/show_bug.cgi?id=14013

Steve, I wish you could make your website/webpage easier to use (referring to colors used, color brightness, color contrast) and also pass validation markup compliance.

Hints:
https://bugzilla.mozilla.org/show_bug.cgi?id=373495

http://validator.w3.org/check?uri=http://steveengland.wordpress.com/2007/07/18/testing-extensions-for-memory-leaks-on-trunk/

Visit 
http://www.mozilla.org/access/authors
and then search for color contrast, color brightness:

    "Contrast is the perceived difference between two adjacent colors. (...) Contrast is extremely important in Web design."
    Wheel of Color: Pump up the Contrast, Robert Hess, MSDN

    "For this year's list of worst design mistakes, (...) I asked readers of my newsletter to nominate the usability problems they found the most irritating. (...) about one-third complained about *_low contrast between text and background_*."
    Top Ten Web Design Mistakes of 2005: 1. Legibility Problems

Respectfully and regards,

Gérard Talbot</description>
		<content:encoded><![CDATA[<p>Ian, the keywords like mlk can be added to a mozdev bug report, but only the reporter or assignee.</p>
<p>Add to the list of resolved memory leakage bug reports at mozdev for Firefox add-on extensions (but without a mlk keyword):</p>
<p>FlashBlock 1.5.1<br />
<a href="https://www.mozdev.org/bugs/show_bug.cgi?id=14013" rel="nofollow">https://www.mozdev.org/bugs/show_bug.cgi?id=14013</a></p>
<p>Steve, I wish you could make your website/webpage easier to use (referring to colors used, color brightness, color contrast) and also pass validation markup compliance.</p>
<p>Hints:<br />
<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=373495" rel="nofollow">https://bugzilla.mozilla.org/show_bug.cgi?id=373495</a></p>
<p><a href="http://validator.w3.org/check?uri=http://steveengland.wordpress.com/2007/07/18/testing-extensions-for-memory-leaks-on-trunk/" rel="nofollow">http://validator.w3.org/check?uri=http://steveengland.wordpress.com/2007/07/18/testing-extensions-for-memory-leaks-on-trunk/</a></p>
<p>Visit<br />
<a href="http://www.mozilla.org/access/authors" rel="nofollow">http://www.mozilla.org/access/authors</a><br />
and then search for color contrast, color brightness:</p>
<p>    &#8220;Contrast is the perceived difference between two adjacent colors. (&#8230;) Contrast is extremely important in Web design.&#8221;<br />
    Wheel of Color: Pump up the Contrast, Robert Hess, MSDN</p>
<p>    &#8220;For this year&#8217;s list of worst design mistakes, (&#8230;) I asked readers of my newsletter to nominate the usability problems they found the most irritating. (&#8230;) about one-third complained about *_low contrast between text and background_*.&#8221;<br />
    Top Ten Web Design Mistakes of 2005: 1. Legibility Problems</p>
<p>Respectfully and regards,</p>
<p>Gérard Talbot</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian</title>
		<link>http://steveengland.wordpress.com/2007/07/18/testing-extensions-for-memory-leaks-on-trunk/#comment-240</link>
		<dc:creator>Ian</dc:creator>
		<pubDate>Thu, 20 Sep 2007 10:19:15 +0000</pubDate>
		<guid isPermaLink="false">http://steveengland.wordpress.com/2007/07/18/testing-extensions-for-memory-leaks-on-trunk/#comment-240</guid>
		<description>A while back I suggested that Mozdev add the 'mlk' keyword for memory leak bugs. There are currently 11 open ones labelled as such, some of which definitely still leak after all this time (e.g. Sage):

https://www.mozdev.org/bugs/buglist.cgi?keywords=mlk

It would be great if Mozilla could help out with these leaks in some situations.</description>
		<content:encoded><![CDATA[<p>A while back I suggested that Mozdev add the &#8216;mlk&#8217; keyword for memory leak bugs. There are currently 11 open ones labelled as such, some of which definitely still leak after all this time (e.g. Sage):</p>
<p><a href="https://www.mozdev.org/bugs/buglist.cgi?keywords=mlk" rel="nofollow">https://www.mozdev.org/bugs/buglist.cgi?keywords=mlk</a></p>
<p>It would be great if Mozilla could help out with these leaks in some situations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gérard Talbot</title>
		<link>http://steveengland.wordpress.com/2007/07/18/testing-extensions-for-memory-leaks-on-trunk/#comment-237</link>
		<dc:creator>Gérard Talbot</dc:creator>
		<pubDate>Thu, 20 Sep 2007 07:58:59 +0000</pubDate>
		<guid isPermaLink="false">http://steveengland.wordpress.com/2007/07/18/testing-extensions-for-memory-leaks-on-trunk/#comment-237</guid>
		<description>Steve,

2 memory leakages where found in previous versions of FireFTP (v. 0.94.6) and then fixed:

https://www.mozdev.org/bugs/show_bug.cgi?id=16409#c1

Obviously, a more systematic examination of all extensions worth using should be done.

Regards,

Gérard
P.S.: Your webpage is so dark that I had to neutralize, override the colors in order to figure out how to reply.</description>
		<content:encoded><![CDATA[<p>Steve,</p>
<p>2 memory leakages where found in previous versions of FireFTP (v. 0.94.6) and then fixed:</p>
<p><a href="https://www.mozdev.org/bugs/show_bug.cgi?id=16409#c1" rel="nofollow">https://www.mozdev.org/bugs/show_bug.cgi?id=16409#c1</a></p>
<p>Obviously, a more systematic examination of all extensions worth using should be done.</p>
<p>Regards,</p>
<p>Gérard<br />
P.S.: Your webpage is so dark that I had to neutralize, override the colors in order to figure out how to reply.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
