<?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: JUnit Memory Usage In Eclipse</title>
	<atom:link href="http://www.symphonious.net/2006/09/19/junit-memory-usage-in-eclipse/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.symphonious.net/2006/09/19/junit-memory-usage-in-eclipse/</link>
	<description>Living in a state of accord.</description>
	<pubDate>Sat, 22 Nov 2008 00:43:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Liu Jinhua</title>
		<link>http://www.symphonious.net/2006/09/19/junit-memory-usage-in-eclipse/#comment-136457</link>
		<dc:creator>Liu Jinhua</dc:creator>
		<pubDate>Fri, 07 Dec 2007 06:48:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.symphonious.net/2006/09/19/junit-memory-usage-in-eclipse/#comment-136457</guid>
		<description>Hi, I have also the same problem. I use Eclipse 3.2 with its builtin juint functionalities. Is there any good solution for this problem (in eclips) for the time being?</description>
		<content:encoded><![CDATA[<p>Hi, I have also the same problem. I use Eclipse 3.2 with its builtin juint functionalities. Is there any good solution for this problem (in eclips) for the time being?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan Alvarsson</title>
		<link>http://www.symphonious.net/2006/09/19/junit-memory-usage-in-eclipse/#comment-96082</link>
		<dc:creator>Jonathan Alvarsson</dc:creator>
		<pubDate>Tue, 03 Jul 2007 11:31:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.symphonious.net/2006/09/19/junit-memory-usage-in-eclipse/#comment-96082</guid>
		<description>I have the exact same problem. Mine occurs at somewhat lower numbers of test though due to the enormous size of things Hibernate and Spring generates for me in each test. Someone said something about using fork to start each test in a new jvm but I am wondering if not this is (only) an Ant feature?</description>
		<content:encoded><![CDATA[<p>I have the exact same problem. Mine occurs at somewhat lower numbers of test though due to the enormous size of things Hibernate and Spring generates for me in each test. Someone said something about using fork to start each test in a new jvm but I am wondering if not this is (only) an Ant feature?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 解惑 &#187; 日志 &#187; 遭遇OutOfMemoryError</title>
		<link>http://www.symphonious.net/2006/09/19/junit-memory-usage-in-eclipse/#comment-44750</link>
		<dc:creator>解惑 &#187; 日志 &#187; 遭遇OutOfMemoryError</dc:creator>
		<pubDate>Mon, 18 Dec 2006 06:19:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.symphonious.net/2006/09/19/junit-memory-usage-in-eclipse/#comment-44750</guid>
		<description>[...] suite的类。   作者: Cherami 原载: 遭遇OutOfMemoryError版权所有。转载时必须以链接形式注明作者和原始出处及本声明。 [...]</description>
		<content:encoded><![CDATA[<p>[...] suite的类。   作者: Cherami 原载: 遭遇OutOfMemoryError版权所有。转载时必须以链接形式注明作者和原始出处及本声明。 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian Sutton</title>
		<link>http://www.symphonious.net/2006/09/19/junit-memory-usage-in-eclipse/#comment-33731</link>
		<dc:creator>Adrian Sutton</dc:creator>
		<pubDate>Tue, 03 Oct 2006 21:12:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.symphonious.net/2006/09/19/junit-memory-usage-in-eclipse/#comment-33731</guid>
		<description>We're using Eclipse 3.2 with JUnit 3.8.2 and JREs from 1.4.0 to 1.6 beta. JUnit 4 might be better but we still support Java 1.4 so don't won't to move our build process up to Java 1.5 and it's too much effort to use two separate JREs for building vs running tests.</description>
		<content:encoded><![CDATA[<p>We&#8217;re using Eclipse 3.2 with JUnit 3.8.2 and JREs from 1.4.0 to 1.6 beta. JUnit 4 might be better but we still support Java 1.4 so don&#8217;t won&#8217;t to move our build process up to Java 1.5 and it&#8217;s too much effort to use two separate JREs for building vs running tests.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Forster Christoph</title>
		<link>http://www.symphonious.net/2006/09/19/junit-memory-usage-in-eclipse/#comment-33698</link>
		<dc:creator>Forster Christoph</dc:creator>
		<pubDate>Tue, 03 Oct 2006 12:26:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.symphonious.net/2006/09/19/junit-memory-usage-in-eclipse/#comment-33698</guid>
		<description>... we experienced the same JUnit behaviour in Eclipse. Our Testsuite contains now over 11000 Unit-Tests and we managed the problem by adding the -Xmx -Xms arguments to the JUnit running configuration.
Today the worst case scenario occured. The testsuite hung up at ~5000 Unit Tests without any exception. Spent the whole day setting new memory values and retry.
Which Java/JUnit/Eclipse version do you use ? We use Eclipse 3.0.1 with JUnit 3.8.1 and JDK 1.5.0.08

Maybe a newer JUnit version will work ?!?</description>
		<content:encoded><![CDATA[<p>&#8230; we experienced the same JUnit behaviour in Eclipse. Our Testsuite contains now over 11000 Unit-Tests and we managed the problem by adding the -Xmx -Xms arguments to the JUnit running configuration.<br />
Today the worst case scenario occured. The testsuite hung up at ~5000 Unit Tests without any exception. Spent the whole day setting new memory values and retry.<br />
Which Java/JUnit/Eclipse version do you use ? We use Eclipse 3.0.1 with JUnit 3.8.1 and JDK 1.5.0.08</p>
<p>Maybe a newer JUnit version will work ?!?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian Sutton</title>
		<link>http://www.symphonious.net/2006/09/19/junit-memory-usage-in-eclipse/#comment-32526</link>
		<dc:creator>Adrian Sutton</dc:creator>
		<pubDate>Tue, 19 Sep 2006 03:01:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.symphonious.net/2006/09/19/junit-memory-usage-in-eclipse/#comment-32526</guid>
		<description>We aren't seeing these problems when the tests are run via ant which is why I suspected the Eclipse plugin. The tests may just be getting more memory when run via ant which would also avoid the problem so it's not guaranteed to be the eclipse plugin.</description>
		<content:encoded><![CDATA[<p>We aren&#8217;t seeing these problems when the tests are run via ant which is why I suspected the Eclipse plugin. The tests may just be getting more memory when run via ant which would also avoid the problem so it&#8217;s not guaranteed to be the eclipse plugin.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse Kuhnert</title>
		<link>http://www.symphonious.net/2006/09/19/junit-memory-usage-in-eclipse/#comment-32525</link>
		<dc:creator>Jesse Kuhnert</dc:creator>
		<pubDate>Tue, 19 Sep 2006 02:52:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.symphonious.net/2006/09/19/junit-memory-usage-in-eclipse/#comment-32525</guid>
		<description>It's not actually just the plugin...As far as I know this is what JUnit does all on it's own..

If you'd like a better alternative that doesn't suck you might try out TestNG instead. It and its eclipse plugin work very well. (It'll also run your junit tests for you to ease the transition..)</description>
		<content:encoded><![CDATA[<p>It&#8217;s not actually just the plugin&#8230;As far as I know this is what JUnit does all on it&#8217;s own..</p>
<p>If you&#8217;d like a better alternative that doesn&#8217;t suck you might try out TestNG instead. It and its eclipse plugin work very well. (It&#8217;ll also run your junit tests for you to ease the transition..)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
