Sometimes when using Eclipse it is possible to receive the following error due to the application running out of memory:
This problem can be more frequent when working with projects that use a lot of libraries and a lot of files, or projects that have a large number of graphical assets. The solution is to to edit the eclipse.ini file and permit FlashBuilder access to larger amounts of RAM.
The eclipse.ini file can be found in OS Lion by navigating to the folder that Flash Builder was installed at which is normally the applications directory. Right or Ctrl + Click the Flash Builder application icon and select ‘Show Package Contents‘ from the menu.
Clicking the ‘Show Package Contents‘ button should open a folder. The eclipse.ini file can be found within the following directory: Contents > MacOS
Open the eclipse.ini file in your favourite text editor. You will need to edit a few of these parameters to enable higher memory. This information from the Adobe website describes the important parameters:
Xms Initial size (bytes) of the memory allocation pool. This value must be a multiple of 1024, greater than 1 MB. Append the letter k or K to indicate kilobytes, or m or M to indicate megabytes.
Xmx Maximum size (bytes) of the memory allocation pool. This value must a multiple of 1024, greater than 2 MB. Append the letter k or K to indicate kilobytes, or m or M to indicate megabytes.
XX:MaxPermSize Maximum size of Permanent Generation
XX:PermSize Initial size of Permanent Generation
Setting these values to higher amounts should stop the error from occurring. I normally set my arguments to the following, and do not often run into any problems:
This should prevent any more out of memory errors. Experiment with the values, but remember to not set them to a value which your machine can not handle.