<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>leaks on Oxymoronical</title>
    <link>https://www.oxymoronical.com/blog/tag/leaks/</link>
    <description>Recent content in leaks on Oxymoronical</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 13 Jun 2007 22:50:37 +0000</lastBuildDate>
    <atom:link href="https://www.oxymoronical.com/blog/tag/leaks/feed/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Easy(er) Leak Testing With NTT</title>
      <link>https://www.oxymoronical.com/blog/2007/06/Easyer-Leak-Testing-With-NTT/</link>
      <pubDate>Wed, 13 Jun 2007 22:50:37 +0000</pubDate>
      <guid>https://www.oxymoronical.com/blog/2007/06/Easyer-Leak-Testing-With-NTT/</guid>
      <description>&lt;p&gt;David Baron recently &lt;a href=&#34;http://dbaron.org/log/2007-06#e20070612a&#34;&gt;put out the call&lt;/a&gt; for there to be more leak testing on trunk builds.Â We have a number of regressions that we need to find and fix before Firefox 3 goes out the door. The best way to do leak testing has always been to use his excellent leak-gauge script which catches more leaks than the leak monitor extension. Unfortunately the leak-gauge script is not the easiest of beasts to play around with.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
