Curing FlexBuilder Memory Bloat

I picked this tip up on the FlexCoders mailing list, which was originally posted on Ted Patick's blog and thought I would share it. It's no secret that if you are working with several open projects at a time in Eclipse (and therefore FlexBuilder), that memory consumption can get out of control, with Eclipse gobbling upwards of a half a gig of RAM or more in some cases. Often times this results in the developer having to kill FlexBuilder to recover the memory and be able to continue work. Some developers have been partitioning separate workspaces for each project, which solves the memory issue, but makes it harder to work with related projects. Fortunately there is an Eclipse plugin called the Kyrsoft Memory Monitor, which can do your garbage collection for you and recover unused memory. The plugin is highly configurable and will allow you to activate automatic GC when RAM consumption reaches a certain threshold. It will also optionally place a small visual usage meter in the status bar.

You can install the plugin from http://www.kyrsoft.com/updates/