<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Memory leak in Ruby 1.8.6 String class</title>
	<link>http://blog.edhickey.com/2008/12/03/memory-leak-in-ruby-186-string-class/</link>
	<description>computers, music, what am i missing?</description>
	<pubDate>Sat, 31 Jul 2010 05:17:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.1</generator>

	<item>
		<title>By: Fix string memory leaks in Ruby 1.8.6 at Topper&#8217;s Blog</title>
		<link>http://blog.edhickey.com/2008/12/03/memory-leak-in-ruby-186-string-class/#comment-5572</link>
		<author>Fix string memory leaks in Ruby 1.8.6 at Topper&#8217;s Blog</author>
		<pubDate>Fri, 04 Sep 2009 15:07:55 +0000</pubDate>
		<guid>http://blog.edhickey.com/2008/12/03/memory-leak-in-ruby-186-string-class/#comment-5572</guid>
		<description>[...] Ruby 1.8.6 leaks memory in some surprising places. Even gsub and split on the String class cause some bad headaches. If you're using Haml and 1.8.6 - you are probably in a bit of trouble. Read more: http://blog.edhickey.com/2008/12/03/memory-leak-in-ruby-186-string-class/ [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Ruby 1.8.6 leaks memory in some surprising places. Even gsub and split on the String class cause some bad headaches. If you&#8217;re using Haml and 1.8.6 - you are probably in a bit of trouble. Read more: <a href="http://blog.edhickey.com/2008/12/03/memory-leak-in-ruby-186-string-class/" rel="nofollow">http://blog.edhickey.com/2008/12/03/memory-leak-in-ruby-186-string-class/</a> [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ed</title>
		<link>http://blog.edhickey.com/2008/12/03/memory-leak-in-ruby-186-string-class/#comment-3849</link>
		<author>Ed</author>
		<pubDate>Wed, 17 Jun 2009 21:07:56 +0000</pubDate>
		<guid>http://blog.edhickey.com/2008/12/03/memory-leak-in-ruby-186-string-class/#comment-3849</guid>
		<description>Alex,
Yes - that looks to be the same bug.  I was using 1.8.4.</description>
		<content:encoded><![CDATA[<p>Alex,<br />
Yes - that looks to be the same bug.  I was using 1.8.4.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://blog.edhickey.com/2008/12/03/memory-leak-in-ruby-186-string-class/#comment-3846</link>
		<author>Alex</author>
		<pubDate>Wed, 17 Jun 2009 19:58:55 +0000</pubDate>
		<guid>http://blog.edhickey.com/2008/12/03/memory-leak-in-ruby-186-string-class/#comment-3846</guid>
		<description>I was wondering what version of ruby 1.8.6 did you use? It appears 1.8.6 p230-p238 had a problem with memory leaks: http://redmine.ruby-lang.org/issues/show/216  I'm wondering if this issue is related or not.</description>
		<content:encoded><![CDATA[<p>I was wondering what version of ruby 1.8.6 did you use? It appears 1.8.6 p230-p238 had a problem with memory leaks: <a href="http://redmine.ruby-lang.org/issues/show/216" rel="nofollow">http://redmine.ruby-lang.org/issues/show/216</a>  I&#8217;m wondering if this issue is related or not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ed</title>
		<link>http://blog.edhickey.com/2008/12/03/memory-leak-in-ruby-186-string-class/#comment-1206</link>
		<author>Ed</author>
		<pubDate>Sat, 17 Jan 2009 18:10:16 +0000</pubDate>
		<guid>http://blog.edhickey.com/2008/12/03/memory-leak-in-ruby-186-string-class/#comment-1206</guid>
		<description>Thanks, Ed.  I'll look into 1.8.7.</description>
		<content:encoded><![CDATA[<p>Thanks, Ed.  I&#8217;ll look into 1.8.7.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ed Anderson</title>
		<link>http://blog.edhickey.com/2008/12/03/memory-leak-in-ruby-186-string-class/#comment-1204</link>
		<author>Ed Anderson</author>
		<pubDate>Sat, 17 Jan 2009 06:18:06 +0000</pubDate>
		<guid>http://blog.edhickey.com/2008/12/03/memory-leak-in-ruby-186-string-class/#comment-1204</guid>
		<description>This was fixed in 1.8.7.</description>
		<content:encoded><![CDATA[<p>This was fixed in 1.8.7.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
