July 14 2009 11:50 AM by Adam
filed under ColdFusion Builder

If you have installed the ColdFusion Builder beta in stand-alone mode, I recommend you update some of the underlying settings before adding in Flash Builder 4 beta. In our attempt to keep ColdFusion Builder lightweight we kept the minimum system requirements as low as possible. The standalone install of ColdFusion Builder only requires 256MB or RAM. Which is all well and good for ColdFusion Builder, but installing other plug-ins like Flash Builder 4 beta ups the requirements. In some cases this could cause ColdFusion Builder to crash on startup or just introduce random java errors.

We'll be sure to update the settings for the final release of ColdFusion Builder to match up with Flash Builder, but in the meantime the fix is pretty easy. Just update a few lines in your eclipse settings file. For the ColdFusion Builder beta standalone install, you can find it under <install directory>\CFBuilder.ini.

Your current settings file probably looks like this:

-startup
plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20081125.jar
--launcher.library
plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731
-vmargs
-Xmx256m

You want to update it to look like this (based on the Flash Builder 4 beta settings):

-startup
plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20081125.jar
--launcher.library
plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731
-vmargs
-Xms512m
-Xmx512m
-XX:MaxPermSize=256m
-XX:PermSize=64m

Of course, these settings are the recommended minimum. If you've got more RAM to spare for Eclipse, it will only improve your experience to set these to higher limits. For more information on optimizing ColdFusion Builder performance check out the MXUnit blog. If you are still curious to know more about eclipse memory settings, this is a handy entry.