[FAQ] JVM heap Low detected

Kunal,

I suspect you meant Xms128m and Xmx768m, right? These are the defaults of CCSv8.

From my experience I have some comments about memory usage:

- To help you monitor this you can enable the heap monitor. Go to menu Window --> Preferences --> General --> Show heap status.

- If you notice there is too much heap memory being used, you can either clean up some by manually running the garbage collector (a small trash can icon on the heap monitor) or increase its size by closing CCS and increasing the -Xmx768m parameter to 1024m in the file <ccstudio.ini> located at %CCS_INSTALL_DIR%\ccsv8\eclipse . Do not increase this too much as it will reduce the available memory for other operations (debugger, etc.) - 32-bit CCS is limited by the 32-bit JVM to 2GB of available RAM. Also, avoid increasing the -Xms128m as it can reduce the available heap that can be freed.

- If your project uses RTSC/TI-RTOS, sometimes opening the .cfg file on the Gconf utility tool can use quite a lot of heap.

- If your project is very large, the indexer can use quite a lot of heap memory while indexing everything.

- If your target configuration has a very large number of devices in the same scan chain, the heap will be exhausted.

- How much physical memory do you have in your system? Although most of the systems nowadays have 4GB of RAM, if you have a lower amount this can be prone to problems.

Unfortunately memory usage is very difficult to minimize due to the thorough mapping performed by the Indexer or the added features on the debugger (register views, etc.). One attempt to reduce this is to disable certain cores to be shown when the debugger is launched (done via the Debug Configurations settings), or disable the indexer or reduce its scope (right click on the Project --> Properties --> C/C++ General --> Indexer - before accessing this option, make sure to click on the Show Advanced Settings link at the bottom of the properties dialog box).

Hope this helps,
Rafael