• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 407 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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/CC2640R2F: Is CCS keyboard lag a sign of a corrupted workspace?

timeslice
Intellectual 290 points

Part Number: CC2640R2F

Tool/software: Code Composer Studio

I've found that pretty often (several times per hour), while I am paging through code, CCS 8 will freeze up for a second or two, and then resume.    If I look at it in Win 10 task manager during the lag, it is taking a full load of one of my CPU cores.     I'm pretty new to CCS so I can't say if this is expected behavior for CCS.   Apart from these incidents, CCS is pretty responsive.

I noticed in the CCS tips & tricks, it is noted that workspaces can get corrupted, and to rebuild them occasionally.   Is this one of the signs I need to rebuild the workspace?

Any other ideas - if it is not the workspace?

  • 0
    TI__Guru**** 483811 points
    These hiccups you see can be caused by a variety of background tasks in CCS. Cleaning your workspace can indeed help. The indexer can also use up a fair bit of resources when it runs, especially if you have large projects imported into the workspace. Rebuilding or even disabling the indexer can help (but disabling it would disable some of the advanced editor functionality). If the source file you are paging through is quite big, it could be the indexer.

    Hope this helps
    ki
  • 0 in reply to Ki
    Intellectual 290 points

    Thanks.  I started a new workspace and now the keyboard lags are gone.   If I go back to my older workspace, they come back.   So yes, definitely workspace related!.