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/TMS320F28335: Code Composer Studio Very Slow Response

Part Number: TMS320F28335


Tool/software: Code Composer Studio

Hello

This is becoming really annoying - but code composer (v8.3.0.00009 on 64-bit Windows 10) has a very slow response in too many situations:

(1) Mark occurrences - when i click on a variable etc in the editor, it is many tens of seconds before it and all occurrences are highlighted.
(2) Windows such as "Preferences" or "Show View" where you "type filter text" to narrow down the choices - it takes a very long time for this to work, if it works at all.
(3) As (2), filtering for keys in the "Preferences > Keys" window.

I found another thread about (1) e2e.ti.com/.../716970 and following that I turn off-then-on "mark occurrences" to speed up the response (a workaround, but not ideal), but have found no way round the others.
As suggested, I tried the "-clean" option, after which (2) might be fixed for one time, but then reappears.  Index rebuild was no help in fixing (1).

This is a problem on at least 3 PCs with CCS 8.3.0 and Windows 10.  I have tried going back to CCS 5 (which I used to use) and all is OK (although not officially supported on W10).

HELP!

Are there any add-ins I could turn off?

  • I deselected various plugins from the list loaded at startup.  Set as in the picture below, the problem has gone.  By default all but "Marketplace Client" are activated.  I don't really know what any of them do, and if needed, but I guess that all those I've deactivated are not needed.

    Any thoughts anyone?

    Thanks.

  • Hello Giles,

    It is an issue that we have unfortunately been plagued with for some time:

    https://e2e.ti.com/support/tools/ccs/f/81/t/659011

    We have made some incremental fixes but of course it has not resolved all the problems. We've never been able to consistently reproduce the issues. Providing the stack thread dumps as mentioned in the above referenced thread can help with additional investigations.

    Turning off the indexer can help - but of course you lose a lot of the editor functionality. 

    Cleaning the workspace can help also. But along with the -clean option, likely the issues will start to reappear after some time.

    As mentioned in previous posts, the size of the workspace in regards to the amount of large open projects can have a great impact (assuming the indexer is enabled). Do you have such an environment?

    Thanks

    ki

  • Hi Ki,

    I created a new, empty workspace.  Even with no projects, after a short while (a minute or two) the filter function in for example the "Show View" dialog stopped working.  This was the behaviour that prompted my post, as some of the dialogs like "Preferences" have so many options, the filter is really needed.

    I have also added the stack thread dump from this workspace.

    Thanks, Giles

     7853.dump.zip

  • Thank you for the dump log. Engineering has analyzed the log and has identified one potential root cause related to automatic updates. Can you disable the automatic update feature in CCS and see if that helps?

    Thanks

    ki

  • Your suggestion above appears to have worked!
    I had already disabled this feature and some plugins as noted above and was no longer seeing the problem.
    So I reset the plugins to the default, re-enabled this feature and closed and re-opened CCS. After a little while the problem re-appeared. It could be when a small pop-up opens saying there are updates available. Disabling the feature again, & re-starting CCS, I find the problem does not appear - all is OK.

    One thing though: As noted above I was able to prevent the problem by disabling the plugins shown above. Re-enabling them brought back the problem. I was not changing the auto-update settings (which was probably disabled), unless one of the plugins is related.

    Many thanks, Giles
  • Great, thanks for trying it out.

    Giles Robnson said:
    As noted above I was able to prevent the problem by disabling the plugins shown above. Re-enabling them brought back the problem. I was not changing the auto-update settings (which was probably disabled), unless one of the plugins is related.

    It is likely an issue with trying to update one (or more) of the plugins. Disabling the plug-in likely meant to CCS that an update for it is not needed. Or it could be that one of the plug-ins that was disabled was related to the update manager.

  • A day later, and things are still OK. Fantastic.
    Thanks again.