This content has been marked as final. Show 5 replies
I seldom have problems with Flex Builder. One thing that might make a difference is turning off automatic compile (as I do). If there is indeed a memory leak in the compiler, having it compile on every save is gonna blow things up greatly.
This has been happening to me as well. I don't mind restarting it every once in a while, but I have noticed my computer becoming a bit slower. I'm on a 1G of ram, and 400mb+ is used by Flex Builded. I have automatic complier turned off and only complie after major changes, so I don't think that could be the problem.
Any help for us?
I've tried your suggestion and turned off the AutoCompile. It does speed things up, but of course the compiling still takes forever, the RAM is still at 400+MB and I would much rather have auto compile activated so that compile time errors are displayed as soon as I save the app and not when I run it, as it is with Java Apps in Eclipse. For now I can live with this workaround, but I think it is something that could be checked into and perhaps be improved.... Thanks a lot though for the tip!
same here guys
are u using the flex builder or plugin for eclipse
me using flex builder.
looking at task bar i have never seen the mem usage drop for javaw even if u close down everything in it.
flex isnt as polised a product as i was hoping it wud be.
adobe doesnt seem to care either as there is no way u can post bugs without a paid subcription