Here are few things I have found. They may help, they may not.
Ultimately I find that projects under version control have been my issues. Let me explain. I have found (at least through SDK 3.0 and 3.1) that an upgrade to the SDK causes the local project file to go through some update but when a later SCM update occurs, you get an old versions project files and crasho. The new SDK is expecting a known project file and gets hair-balled by what came in from source control. I have tried cutting and pasting another copy, reverting, trying to fix by hand, etc but in the end, I find that I have had to create a new blank project and copy all the files (except for the project files) and reconfigure the library path, and the rest of the goo. You will need the new library properties, and other . (dot) files as well from the new project. Bring in the old ones and you die. I'll bet you can close each of your projects and the crashes will stop when the offending project(s) is closed. The list of source files to be compiled can be corrupted. I believe this is the real issue with reverting project files but don't have a good handle on why - but you should try disabling incremental compilation. Add "-incremental=false" to the compiler settings in the Flex Compiler tab of the Properties. This will effectively ignore the .cache files. Compile times will be longer - but hopefully that is offset by having a stable environment. Flex uses cache files to persist previously compiled objects. And a clean build doesn't necessarily refresh the cache files. It is benign to backup and remove those .cache files. They live in a few places so you will need to find the .metadata/.plugins/org.eclipse.core.resources/.projects directory and within that directory, you will find one for every Flex project. For example ./metadata/.plugins/org.eclipse.core.resoures/.projects/MYPROJECT/com.adobe. flexbuilder.project/MyProject.cache. For each release, I like to clean these out regardless. K From: [email protected] [mailto:[email protected]] On Behalf Of Geoffrey Sent: Thursday, April 30, 2009 11:30 AM To: [email protected] Subject: [flexcoders] Eclipse Crashing Recently, FB(Eclipse) keeps crashing on me. I've looked all over the place for solutions, have tried many, but none seem to do the trick. My current setup is: Eclipse 3.4.2 (M20090211-1700) FB 3.0.2.214193 Flex SDK 3.3 JDK 1.6.0_13 My eclipse.ini is: -showsplash org.eclipse.platform -framework plugins\org.eclipse.osgi_3.4.3.R34x_v20081215-1030.jar -vm C:\Program Files (x86)\Java\jdk1.6.0_13\bin\javaw.exe -vmargs -Xms1024M -Xmx1024M -XX:PermSize=256M -XX:MaxPermSize=512M -XX:+UseParallelGC -Dosgi.requiredJavaVersion=1.5 -Djava.net.preferIPv4Stack=true -Dcom.sun.management.jmxremote Our Flex application is a collection of 30 projects (one main one and 29 flex library projects). All have to be open at the same time or else you get build(dependency) errors. There's a few projects that are linked to many of the other projects. For example, we have a project that holds all of the VOs. Making changes to that project always took a long time to build (several minutes), but now it crashes with OutOfMemory errors. I've run jconsole to watch the JVM performance statistics. I don't fully understand all the numbers, but I can see that my PS Old Gen pool gets 100% full, and that's when I usually expect a crash to happen soon. My machine has 8GB of RAM, although I can only allocate 1GB to Eclipse it seems. If I raise -Xmx higher than 1024M, Eclipse won't even start. Anyone have any suggestions? Thanks, ~Geoff
