<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: AVG 9.0 Free Sucks for Gamers</title>
	<atom:link href="http://tarandon.ca/technology/143/feed/" rel="self" type="application/rss+xml" />
	<link>http://tarandon.ca/technology/143/</link>
	<description>Life would be much easier if I had the source code.</description>
	<lastBuildDate>Fri, 15 Jan 2010 03:43:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Randy</title>
		<link>http://tarandon.ca/technology/143/comment-page-1/#comment-53</link>
		<dc:creator>Randy</dc:creator>
		<pubDate>Fri, 15 Jan 2010 03:43:50 +0000</pubDate>
		<guid isPermaLink="false">http://tarandon.ca/?p=143#comment-53</guid>
		<description>If you do buy the AVG 9.0, be aware that there is a huge problem with avgfws9.exe consuming a large percentage of CPU cycles, hogging memory, and continually thrashing the C drive (probably due to rapid allocation/deallocation of large amounts of memory).  This still exists in the 725 build (most recent) and they claim it will be fixed in the next update, but who knows when that will be.  I wonder how many drives AVG has destroyed with this defect?  A problem like this should never make its way into a release build.  It sucks.  No wonder there&#039;s no public forum for actual customers.</description>
		<content:encoded><![CDATA[<p>If you do buy the AVG 9.0, be aware that there is a huge problem with avgfws9.exe consuming a large percentage of CPU cycles, hogging memory, and continually thrashing the C drive (probably due to rapid allocation/deallocation of large amounts of memory).  This still exists in the 725 build (most recent) and they claim it will be fixed in the next update, but who knows when that will be.  I wonder how many drives AVG has destroyed with this defect?  A problem like this should never make its way into a release build.  It sucks.  No wonder there&#8217;s no public forum for actual customers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
