<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>LolocoJr &#187; gettext leakage</title>
	<atom:link href="http://www.railsguru.com/articles/tag/gettext-leakage/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.railsguru.com</link>
	<description>Andy Lo-A-Foe&#039;s blog</description>
	<lastBuildDate>Fri, 09 Jul 2010 12:08:16 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Massive memory leak in ruby-gettext 1.90.0</title>
		<link>http://www.railsguru.com/articles/2008/05/08/massive-memory-leak-in-ruby-gettext-1-90-0/</link>
		<comments>http://www.railsguru.com/articles/2008/05/08/massive-memory-leak-in-ruby-gettext-1-90-0/#comments</comments>
		<pubDate>Thu, 08 May 2008 20:38:00 +0000</pubDate>
		<dc:creator>andy</dc:creator>
				<category><![CDATA[Home]]></category>
		<category><![CDATA[rails]]></category>
		<category><![CDATA[gettext leakage]]></category>

		<guid isPermaLink="false">http://www.railsguru.com/2008/10/27/massive-memory-leak-in-ruby-gettext-1-90-0</guid>
		<description><![CDATA[Just found out there&#8217;s a massive memory leak in ruby gettext 1.90.0, one of our applications started eating GBs of RAM after a couple of days in use. So If you&#8217;re using gettext for translating your Rails app take note! You can grab the current trunk which has a fix for this.]]></description>
			<content:encoded><![CDATA[<p>Just found out there&#8217;s a massive memory leak in ruby gettext 1.90.0, one of our applications started eating GBs of RAM after a couple of days in use. So If you&#8217;re using gettext for translating your Rails app take note! You can grab the <a href="http://rubyforge.org/scm/?group_id=855" target="_blank">current trunk</a> which has a fix for this.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.railsguru.com/articles/2008/05/08/massive-memory-leak-in-ruby-gettext-1-90-0/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
