<?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"
	>
<channel>
	<title>Comments on: Waiting on Flex Builder</title>
	<atom:link href="http://www.rogue-development.com/blog2/2007/08/waiting-on-flex-builder/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rogue-development.com/blog2/2007/08/waiting-on-flex-builder/</link>
	<description>Comments and thoughts on technology from Marc Hughes</description>
	<pubDate>Wed, 07 Jan 2009 11:56:35 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Kevin</title>
		<link>http://www.rogue-development.com/blog2/2007/08/waiting-on-flex-builder/#comment-61</link>
		<dc:creator>Kevin</dc:creator>
		<pubDate>Fri, 17 Aug 2007 13:59:00 +0000</pubDate>
		<guid isPermaLink="false">http://rogue-development.com/blog2/?p=44#comment-61</guid>
		<description>Not sure if it'd help, but I like to increase the amount of ram that flex builder is allowed to use with the command line args -Xmx.  Like eclipse.exe -vmargs -Xms128m -Xmx512m.</description>
		<content:encoded><![CDATA[<p>Not sure if it&#8217;d help, but I like to increase the amount of ram that flex builder is allowed to use with the command line args -Xmx.  Like eclipse.exe -vmargs -Xms128m -Xmx512m.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IanT</title>
		<link>http://www.rogue-development.com/blog2/2007/08/waiting-on-flex-builder/#comment-60</link>
		<dc:creator>IanT</dc:creator>
		<pubDate>Fri, 17 Aug 2007 13:49:00 +0000</pubDate>
		<guid isPermaLink="false">http://rogue-development.com/blog2/?p=44#comment-60</guid>
		<description>It could be Java rather than Flex per se.&lt;br/&gt;&lt;br/&gt;Every so often, Java's garbage collection routines kick in, severely slowing down everything else. I suspect at about the point you perform a build, Eclipse asks for a lot more resources, Java realises it should clean up, and then spends ages cleaning up.&lt;br/&gt;&lt;br/&gt;It's often like that with UI-heavy (and therefore object-heavy) apps...</description>
		<content:encoded><![CDATA[<p>It could be Java rather than Flex per se.</p>
<p>Every so often, Java&#8217;s garbage collection routines kick in, severely slowing down everything else. I suspect at about the point you perform a build, Eclipse asks for a lot more resources, Java realises it should clean up, and then spends ages cleaning up.</p>
<p>It&#8217;s often like that with UI-heavy (and therefore object-heavy) apps&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keith Peters</title>
		<link>http://www.rogue-development.com/blog2/2007/08/waiting-on-flex-builder/#comment-59</link>
		<dc:creator>Keith Peters</dc:creator>
		<pubDate>Fri, 17 Aug 2007 13:32:00 +0000</pubDate>
		<guid isPermaLink="false">http://rogue-development.com/blog2/?p=44#comment-59</guid>
		<description>Yeah, FlexBuilder definitely seems haunted sometimes. Good hints here.</description>
		<content:encoded><![CDATA[<p>Yeah, FlexBuilder definitely seems haunted sometimes. Good hints here.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
