MK Partners
Fixing the Eclipse Memory issue
A few weeks ago I upgraded to eclipse 3.4 and the latest version of the Force.com IDE. Since then I have been constantly plagued by Out of Memory errors and have not only experienced extreme frustration but also decreased productivity. Last night while migrating configuration from sandbox to production I finally got fed up with it and decided to take some action. After scouring various posts on message boards I came across this thread indicating that the following three parameters should fix the problem:
-vmargs
-Xms128m
-Xmx512m
Before editing your eclipse.ini file (located in the folder containing the eclipse executable), you should make a backup copy, just in case something goes wrong (which is unlikely). Once you edit it, you’ll probably already see the -vmargs parameter. You might also see the -Xms and -Xmx parameters but set to different numbers. If you do see them, change the numbers to those above. If you don’t see them then add them. Save the .ini file and launch eclipse, and forget about your memory problems.
2 Comments to "Fixing the Eclipse Memory issue
I’m sure you know this already, but in case you have a lot of memory, you could up the -Xmx flag even more. If you use Eclipse a lot, why not give it 1Gb (-Xmx1024m) or even 1.5 Gb(-Xmx1536m)?
512 Mb isn’t much these days, at least for an application like Eclipse. =)
Salesforce.com recommends against using the Force.com IDE with Eclipse 3.4. As of the Summer ’08 release of the IDE, we have not tested it with the new Eclipse (released after the IDE) and we have heard of some obscure but serious issues, which I’ve posted about in the forums on developer.force.com.