[news.eclipse.tools.jdt] Re: How to prevent out of memory errors?

[james_adams@xxxxxxxxx (James Adams)]

Thanks Thorbjørn.

Lately I've been developing an application which uses Spring, Hibernate, 
and JMS.  I typically launch many JUnit/DbUnit tests which may incorporate 
an embedded ActiveMQ broker and/or an in-memory HSQLDB database.  My DAO 
tests may also connect with an Oracle DataSource.  I use 
Subversion/Subclipse for checking in code.  Overall I don't think I'm 
doing anything out of the ordinary.

java -version:
java version "1.6.0_01"
Java(TM) SE Runtime Environment (build 1.6.0_01-b199)
Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode, sharing)

java -fullversion:
java full version "1.6.0_01-b199"

My Windows XP JAVA_HOME environment variable is set to a 1.5 JDK base 
directory since I am using Java 1.5 for my development.

My JRE preference setting in Eclipse was set to a 1.5 JRE, and I have now 
changed it to the 1.6 JRE, which will hopefully make some difference.


--James



Thorbjørn Andersen wrote:

> James Adams skrev  den 25-12-2006 03:09:

> > mind that Eclipse is the only program I run on this system which crashes 
> > because it runs out of memory, and it happens when there is a full 1Gb 
> > or more of memory to spare.  Fortunately when this sort of crash happens 

> It is not because your JVM cannot get any more memory from your 
> operating system, but because some internal data structure to the JVM 
> runs full.

> I have never seen this message so I was wondering if perhaps it is your 
> basic Java installation or work pattern that is different from mine.

> What does "java -version" and "java -fullversion" report on your system? 
>   Could you elaborate on what you actually DO with Eclipse?

> Could you try the new Java 1.6 from Sun?