This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS: PC memory leak caused by CCS

Other Parts Discussed in Thread: CCSTUDIO

Tool/software: Code Composer Studio

I believe CCS 7.1.0 on Windows 10 (tested for version 1703 build 15063.108, version 1703 build 15063.1155, and version 1709 build 16299.461) leads to memory leak. After rebooting the system and starting only CCS with an empty workspace, it’s easily to run out of 8GB RAM overnight. I also tested the same situation with Antivirus disabled. This becomes an issue when I have to use CCS for a whole day because I have to stop all my ongoing tasks/applications and reboot the system. I searched online and it seems other people encountered the same problems (even on Win7 and MUCH earlier CCS versions). I'll just paste one here for example:
https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/601740?CCS-LAUNCHXL-CC1310-CCS-memory-leaks

When I installed CCS 7.1.0, I chose "66AK2x multicore DSP + ARM Processors & C66x Keystone multicore DSP" for "Processor Support"
and "Spectrum Digital Probes and Boards" for "Select Debug Probes"

Does anyone has any patch that can fix this issue on CCS7.1.0? Due to some private SDK compatibility issues, I cannot upgrade CCS version for now. But I guess the most recent CCS version still has this problem.

  • Hello,
    I have heard reports of various memory leaks but we've never been able to reproduce the issue. I will try again to see I can reproduce the issue, this time on Win 10-64 v1709. I will let it run overnight and update you of my progress.

    Thanks
    ki
  • Thank you! Looking forward to your result. I've tested it many times very carefully over the past month (on two different desktop, one OS was freshly installed), and strongly believe this issue exists.

  • I experimented using a slightly newer version of CCS (v7.3) on my Windows 10-64 build 1709 PC. Using an existing workspace with a few project imported, I left it running early last evening to this morning (about 14 hours). There was no increase in RAM usage.

    When you mentioned "After rebooting the system and starting only CCS with an empty workspace, it’s easily to run out of 8GB RAM overnight.", how much usage did CCS have during this time? And what views were open? Would you see the memory leak when simply starting up CCS with an empty new workspace and then just left alone?

    Thanks
    ki
  • Are you checking the memory usage by CCS only or the total memory used by the system? There won't be any memory usage increase in CCS, but the total memory used by the system is increasing.

    Answer to your questions:
    "After rebooting the system and starting only CCS with an empty workspace, it’s easily to run out of 8GB RAM overnight.",
    how much usage did CCS have during this time? => always around 400MB, but please check the total memory used by the system
    And what views were open? => "Project Explorer" and "Getting Started"
    Would you see the memory leak when simply starting up CCS with an empty new workspace and then just left alone? => YES
  • YW said:
    Are you checking the memory usage by CCS only or the total memory used by the system?

    Both. CCS was using ~380MB and the total memory being used by the system was around 3.9GB at the time. 14 hours later, both number were around the same. 

    I did use a slightly later version of CCS. This time, I will use the same exact version (7.1) and try again

    Thanks

    ki

  • Thank you so much Ki. When you install CCS 7.1.0, could you please choose "66AK2x multicore DSP + ARM Processors & C66x Keystone multicore DSP" for "Processor Support" and "Spectrum Digital Probes and Boards" for "Select Debug Probes"?

  • YW said:
    When you install CCS 7.1.0, could you please choose "66AK2x multicore DSP + ARM Processors & C66x Keystone multicore DSP" for "Processor Support" and "Spectrum Digital Probes and Boards" for "Select Debug Probes"?

    I installed this exact setup and run my test again (launched CCS with a new workspace and then left it running with just the Getting Started and Project Explorer views open). It started out with ccstudio.exe using 379.3 MB and the overall system usage at 4.4 GB. After leaving it running for ~10 hours, the memory usages was 380.6MB/4.5GB. Hence not much of an increase was observed. This memory leak is likely environment specific since attempts to reproduce previously reported issues were also unsuccessful. I will need to talk with the engineers to come up with another way to track the memory leak and let you know. We are still investigating

    Thanks

    ki

  • Hmmm... interesting. I'll test CCS 7.1.0.00016 on my personal laptop next week and get back to you. The previous machines I tested are all from my company. Thank you so much for your time and effort. :)

  • My personal laptop doesn't show memory leak either. I reinstalled one desktop in my company with Win10 image from Microsoft instead of our customized Win10 image, and there is no memory leak at all. Now I'm testing a machine which showed memory leak before even with antivirus disabled. But this time I "uninstall" its antivirus. Will report the new result tomorrow.
  • I tested the memory usage with antivirus (FortiClient) uninstalled. And there is no memory leak anymore. However even if FortiClient is installed, as long as CCS is not started, there is no memory leak as well. I don't know whether it's possible to have a CCS patch so it won't be affected by FortiClient, but finally the problem is narrowed dow.

  • Thanks for the update. There is likely some issue between the two. I am not certain if a fix needs to come from the CCS side or if it is a bug with FortiClient. I will try to reproduce on a spare machine for more analysis.

    ki
  • Thank you for the follow-up. I totally agree with you. And since I reported this issue to our network admin group two weeks ago, they haven't found a solution yet so I'm using other Antivirus without memory leak problem anymore.
  • I installed Forticlient v6 on my home PC (i could not download it on my company network) with the default options. I then left it running along with CCSV8. I let it run overnight and no memory leak was observed this morning. It may be some specific settings of forticlient or something else in the environment. Any more details on your setup (and forticlient configuration) wad be helpful.

    Thanks
    ki
  • I'm not sure whether there is some specific windows setting causing this problem as our company has a customized Win10. But without FortiClient installed, both the original Win10 and our customized Win10 don't show any memory leak. Since our FortiClient has a central server management, I cannot try FortiClient on original WIn10 due to registration requirement.

    As for the FortiClient settings, please refer to the screenshots below of one machine I found memory leak. Also when I was testing the memory leak, I found that it's not the antivirus part of FortiClient causing memory leak. When I shutdown its antivirus part, other processes such as logging and telemetry of FortiClient were still running and cause memory leak. I suspect it's those background FortiClient process which communicate with central server messing up the memory.

  • Hi Ki,

    as you wrote that your CCS uses only 379 MByte, I ask me what small workspace your are using? Please would you activate the CCS indexer and load a real DSP project with some static libraries and 100 of source files, e.g. for a LTE base station or a DAB receiver, both coded with C++, and run the compiler. After them you will see that the CCS will running out of the memory sometimes. Also the usage of the debugger will close (break) the CCS.

    I am using the max. usable memory setting -Xmx2000m. With that my CCS v8.1.0 is using 1.300 MByte on Windows 7 prof. 64bit.

    Kind regards
    Sven