First off, are you running 32 bit or 64 bit Java? Not to mention Eclipse (Flash 
Builder). NB: Flash Builder is built on Eclipse. It looks like it is 32 bit 
(win32 mentioned in plugins line). This will give a maximum heap size of 2GB 
which you would not be able to set it to as there would not be any memory left 
to work with. Also, a DLL may have loaded into the memory area that the JVM 
wants to use for heap (The JVM needs a contiguous block of memory). Java is 
intelligent enough to give an error if you set initial(Xms) or maximum(Xmx) 
heap size too high.

Some posts that might help you understand these settings...

--- In, Mike Slinn <msl...@...> wrote:
>   The source code in my message did not look the same in the daily 
> digest as it did online.  I will try posting once again; the biggest 
> memory allocation that I can currently specify in FlashBuilder.ini file is:
> -nl
> en_US
> -startup
> plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
> --launcher.library
> plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.200.v20090519
> -vmargs
> -Xms800m
> -Xmx800m
> -XX:MaxPermSize=384m
> -XX:PermSize=128m
> Also, I have seen a report that running Eclipse from a JDK gives more 
> memory control than from a JRE.  That did not make sense to me, but I 
> tried it anyway, by changing the shortcut properties to:
> "E:\Program Files\Adobe\Adobe Flash Builder 4\FlashBuilder.exe" -vm 
> "E:\Program Files\Java\jdk1.6.0_20\bin"
> vs.
> "E:\Program Files\Adobe\Adobe Flash Builder 4\FlashBuilder.exe" -vm 
> "E:\Program Files\Java\jdk1.6.0_20\jre\bin"
> I did not find any difference.
> Mike

Reply via email to