Looks like this is been a common error for almost memory intensive applications now-a-days. I have been working on eclipse for a long time and recently with the Eclipse + Java 1.5.0_04 + EMF + WTP combimation of installation, i have been seeing the error more often.
Its been quite emberrasing to see such errors on the client machines and especially when i was not sure of the problem and the root of the cause. In anycase after going through couple of documents on the java and eclipse news groups, looks like this problem can be avoided if we set some jvm arguments. Some also suggest that if we use IBM’s Java, it would be solved. But i have not changed the Java from Sun to IBM but just the vm arguments works.
It can be done in few different ways…
- Set the arguments in the Run or Profile windows of eclipse -XX:PermSize=128M -XX:MaxPermSize=256M
- Set the arguments in eclipse.ini file in eclipse home directory
- Set these programmatically…
In my case i have the following vm agrs already set 🙂
-Xms256m
-Xmx1024m
-XX:PermSize=128M
-XX:MaxPermSize=256M
Few other sources to get more info…
http://www.brokenbuild.com/blog/2006/08/04/java-jvm-gc-permgen-and-memory-options/
This solution worked great for me.