|
Hey All, I have
tried the following with reference to the below article. -vmargs -Xms512M -Xmx1024M It still doesn’t work…
Any help would be greatly appreciated. /////////////////////////////////////////ARTICLE/////////////////////////////////////// I have tried this but it
failed to help. Flex Builder running slow or
hang, or get "out of Memory" message Flex Builder will consuming
memory over times, especially when you have a lot of projects created in FB.
You can monitor the memory usage of FB from windows task manager. Look at the
javaw.exe process, the above mentioned problems usually happens when the memory
usage of javaw.exe is too height. You can close and restart
the FB to clean up the memory. By default, FB set the heap
size for Java virtual machine in FlexBuilder.ini as following: -vmargs -Xms256M -Xmx512M If you exceed the maximum
value, "OutOfMemory" errors can occur. If your system has more
total memory available, then you can increase the maximum heap size value. The
rule of thumb used to be set the maximum heap size no more than half of the
total memory available. However, with the new features and settings in the newer
version of JDK, there are more factors you need to consider when deciding what
is the best maximum heap size you can use. You can consult articles about heap
size online. To change the heap size
settings, you can modify them in FlexBuilder.ini under the FB root directory. If you start FB by command
line (or using Eclipse), then you can change them by command line (or FB2
shortcut) such as "C:\Program Files\Adobe\Flex Builder 2 Beta
1\FlexBuilder.exe" -vmargs -Xms256M -Xmx512M 7. NullPointer Exception when
open FB If you leave some files open
when you close FB and restart FB later, by default FB will open the files you
previously opened. If one of those opened file has been deleted already at this
time, then FB will throw NullPointer exception. All you need to do to get rid
of the exception is to close that file.
From:
[email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Hey All, I am seeing the following error right now
“An out of memory error has occurred. You can prevent
these errors in the future by increasing your heap size before you start the
workbench using the –vmargs –Xmx command line option” Any help would be greatly appreciated. Thanks
| |||||||||||||
