This content has been marked as final. Show 10 replies
Actually, the comments about garbage collection apply to Flex Builder as well
as to Flex. Flex Builder is written entirely in Java.
So, there aren't any real "leaks" in the sense you are describing; but
certainly it's true that Flex Builder does use a whole lot of memory, and we
should spend some time working on reducing our memory usage.
Thanks for the feedback. - Mike
Mike: it's still possible to have memory leaks in Java.
Jim: it's possible that nothing is leaking at all. Java is not required to ever run the garbage collector, and maybe your 2GB of RAM is giving it plenty of stretching room. On my half-gig windows machine the java process also eats a load of RAM the first time I compile, but after a few times it tops out at 194MB.
> Mike: it's still possible to have memory leaks in Java.
Yes, I know, but for one thing, Jim was under the impression that Flex Builder
was not doing garbage collection, and I wanted to correct that impression; and
secondly, we know from analysis that the memory consumption issues in Flex
Builder are not caused by leaks, just by using more memory than we should.
Thanks - Mike
Semantic hair-splitting aside, FB2 suffers from unbounded memory
consumption - in products that I've developed, this was labelled a "memory
I provided the following to Adobe as part of feedback for the GMC6 build.:
The test below exposed a memory loss of about 70 MB over 2 hours.
Eclipse plug-in, javaw started with -Xmx768M
1.. Open editor on Explore.mxml. Switch to Design view and back to
2.. Compile older revision 191 of Flex source files, then compile latest
revision. Note Mem Usage value. Repeat step 2.
Windows Task Manager Mem Usage
573 Error: Couldn't get content type
Just wanted to add to the growing list of users experiencing memory issues. I have 2GB of memory on my dev box but after about two or three hours I run out of memory and the builder crashes. After the builder crashes, the system memory jumps back up and I can re-launch the builder app again (I save very often so its more an annoyance than anything else). This repeats several times in the course of a development session. The few times I've watched my system resources, I can see the javaw process consuming large quantities of memory (~256-512MB at one point). Anyway, just wanted to add my input since I'm affected as well.
You can try using different JVM with the Flex Builder to see if it helps.
(prefered method in the comments)
Sun's Java HotSpot might have some memory leaks try using IBM's VM or JRockit and see if it helps the Flex Builder memory issues.
Do you have a source for your claim of a memory leak in the Sun VM? Which
version(s) of the JRE/JDK?
Sorry about hte Sun memory leak comment, I shouldn't claim anything but there is a lot of chatter since Flex about different issues. Either way if you are having problems with compiling it doesn't hurt to try different VM arguments or different JVM's.
Other known issues:
Compiler is slow with Sun JRE 1.4.2_10 - There is a known issue with Sun JRE 1.4.2_10 with unzipping that causes the compiler to be extremely slow. This issue is not present in Sun JRE 1.4.2_09 or Sun JRE 1.4.2_11.
Now on the other hand. JVM's in general eat up Ram normally and don't give it back even if they are doing garbage collection. You can set Xmx and Xms settings to limit the start and max ram the JVM should use.
Im using XP pro service pack2 and 1GB ram, I will admit then when i launch FB and the first time i compile it eats about all my memmory but after that javaw grabs about 220MB and thats about it, i leave my maching on for days, play games and movies and generally abuse my poor machine but no problems running out of ram.
i use Sun's JVM and Jrockits with 2 eclipses (Flex 1.5 and Flex2), ColdFusion and Tomcat. I have 2 GB of ram and I develop on my box all day at work with no problems too. But I have had servers that have issues with different JVM and their settings.