Right now, as I post this, I’m waiting for FlexBuilder to do whatever it is that it does. I’ve looked around but have yet to find a suggestion on why occasionally it’ll just take a minute or more to refresh & build. Arghhh.
Some suggestions that have made it better for me (but not 100% better)…
Project->Properties->Flex Applications …
make sure only the ONE main mxml file you care about is listed there.
Project->Properties->Flex Compiler …
Turn on “Generate HTML template”.
Turn off “Copy non-embedded assets” (if you do that, you’ll have to remember to refresh your assets by copying them to your bin folder when they change.)
There’s certain JRE versions to stay away from, when I upgraded to 1.6.something it got a lot better for me.
Occasionally, edit your .actionscriptproperties and remove “weird crap” that’s in there. I’ve seen refereneces in there like “src/src/src/src/src/src/src” for some unknown reason.
Yeah, FlexBuilder definitely seems haunted sometimes. Good hints here.
It could be Java rather than Flex per se.
Every so often, Java’s garbage collection routines kick in, severely slowing down everything else. I suspect at about the point you perform a build, Eclipse asks for a lot more resources, Java realises it should clean up, and then spends ages cleaning up.
It’s often like that with UI-heavy (and therefore object-heavy) apps…
Not sure if it’d help, but I like to increase the amount of ram that flex builder is allowed to use with the command line args -Xmx. Like eclipse.exe -vmargs -Xms128m -Xmx512m.