<?xml version="1.0" encoding="utf-8" ?>
<rss version="2.0" xmlns:osnews="http://osnews.com/rss2#">
	<channel>
		<title>OSNews: </title>
		<link>http://www.osnews.com/story/16698/Resolve_Memory_Leaks_Using_AIX_5_3</link>
		<description>Exploring the Future of Computing</description>
		<language>en-us</language>
		<copyright>Copyright 2001-2009, David Adams</copyright>
		<webMaster>adam+nospam@osnews.com</webMaster>
		<lastBuildDate>Tue, 10 Nov 2009 11:54:20 GMT</lastBuildDate>
		<image>
			<url>http://www.osnews.com/images/osnews.gif</url>
			<title>OSNews.com</title>
			<link>http://www.osnews.com</link>
		</image>
		<item>
			<title>maybe</title>
			<link>http://osnews.com/thread?191284</link>
			<guid isPermaLink="true">http://osnews.com/thread?191284</guid>
			<description>this should be sent over to the firefox team?<br />
<br />
*notices all of the evil looks*  What WHAT!!?!?!<br />
<br />
Sorry, lol.....   I couldn't help it.  I know that memory leaks are a big complaint for some, perhaps they could do some developing on AIX machines to clean all of this up?<br />
<br />
I'm just saying.................</description>
			<pubDate>Tue, 12 Dec 2006 19:54:00 GMT</pubDate>
			<author>donotreply@osnews.com (halfmanhalfamazing)</author>
			<category>Comments</category>
		</item>

		<item>
			<title>Use good tools</title>
			<link>http://osnews.com/thread?191311</link>
			<guid isPermaLink="true">http://osnews.com/thread?191311</guid>
			<description>How about programming in a language that automates memory (de)allocation? There, no more memory leaks.</description>
			<pubDate>Tue, 12 Dec 2006 20:46:00 GMT</pubDate>
			<author>donotreply@osnews.com (Sodki)</author>
			<category>Comments</category>
		</item>

		<item>
			<title>RE: Use good tools</title>
			<link>http://osnews.com/thread?191590</link>
			<guid isPermaLink="true">http://osnews.com/thread?191590</guid>
			<description>Actually, you can still have memory leaks even in languages that garbage collect or do reference counting. It's not hard to add an object to some collection and then forget about. The collection just grows and grows until you run out of memory. Granted, it's easier to find what is growing, because you can tell the JVM to dump it's heap into a file for inspection.<br />
<br />
Also, languages that do GC have the downside of actually cleaning up their memory space when they start running out of space, which causes pauses and general slowness. And nobody likes that.</description>
			<pubDate>Wed, 13 Dec 2006 05:58:00 GMT</pubDate>
			<author>donotreply@osnews.com (pojo)</author>
			<category>Comments</category>
		</item>

		<item>
			<title>RE[2]: Use good tools</title>
			<link>http://osnews.com/thread?191597</link>
			<guid isPermaLink="true">http://osnews.com/thread?191597</guid>
			<description>When I use to program in BASIC I would call the FREE() function to force Garbage Collection when I wanted it done.  Among other things if you called it often each FREE() took very little time to run.<br />
<br />
Don't all languages that do GC allow you to force it early to control delays?</description>
			<pubDate>Wed, 13 Dec 2006 06:16:00 GMT</pubDate>
			<author>donotreply@osnews.com (Earl Colby pottinger)</author>
			<category>Comments</category>
		</item>

		<item>
			<title>Uh</title>
			<link>http://osnews.com/thread?191615</link>
			<guid isPermaLink="true">http://osnews.com/thread?191615</guid>
			<description>Nice that this OS everyone forgot about which would not run on any of your computers anyways has this neat feature<br />
<br />
But what about using memory leak detectors for detecting memory leaks instead?<br />
Valgrind comes to mind</description>
			<pubDate>Wed, 13 Dec 2006 07:56:00 GMT</pubDate>
			<author>donotreply@osnews.com (grfgguvf)</author>
			<category>Comments</category>
		</item>
	</channel>
</rss>
