CCS/CODECOMPOSER: Java heap space issues

Hi Jan,

I am assuming that you are on Windows since the vast majority of these "out of memory" and heap space issues occur on CCS for Windows. This is because CCS for Windows is still a 32-bit application (we are planning have CCS be 64-bit starting with CCSv9) and hence runs into the 2GB limit on Windows.

Jan Gustav Heber said:

I have increased the Xmx size in the eclipse.ini file first to 1024 then to 2048 without getting rid of the error messages. When I try to increase the size to above 1024 in ccs.ini, ccs won't start at all.

There is a "sweet spot" in regards to the max heap size for CCS. 768m to 1024m seems to be it. Any greater and you could run into the issues described above. The best value requires some experimentation. Looks like 1024m is it in your case. Note that it is ccstudio.ini that must be modified, not eclipse.ini. 

Certain features in CCS can use up a lot of memory. When you get these warnings, what does you CCS environment look like? Are you in a debug session? And if so, for which target? Do you have many views open? If a program is loaded, how large is the executable file you loaded? Did you use the Stack Usage view? Any additional information about your environment will be helpful.

You can also try using a new workspace folder in case you current one got corrupted. You can also try disabling the indexer. 

Thanks

ki

Hi!

Sorry that I left out some vital information. Yes, I am running the CCS on Windows 10. After some research today, I found out that one file caused the problem. Every time this file was present in the editor, I got the warning. Trying to alter the content of the file did not help, but removing it from the solution and adding the same file with a different name seems to solve the problem. I guess I could live with this workaround, however it would be nice to keep the filename as I use GIT to track changes. An alternative might probably be to clear the workspace and create a new one as recommended on your wiki pages. Do you think a simplified approach could solve the problem, just deleting the old project file and then create a new one?

Best regards,
Jan

That is quite interesting. I can't imagine the file name itself being the culprit. Can you try rebuilding the index for the project? Perhaps the index was corrupted, specifically the index for that particular (previously named) file. You can also try cleaning your workspace folder.

Thanks
ki

Hi!

I tried to clean my workspace folder running ccs with the clean option without any luck.  How do I reset the index for the file in question?

Best regards,

Jan

Thanks, the rebuild of the index did the trick. No more Java heap warnings!

Regards,

Jan