• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 4924 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

C/C++ Workspace/Indexer slowdowns

Ki
Guru**** 450031 points
Other Parts Discussed in Thread: CCSTUDIO

Tool/software: Code Composer Studio

Hello,

There has been a recent spike in reported issues with the Eclipse CDT Indexer since CCSv7.x, which has led to big slowdown/hangs of the CCS environment.

Some examples:

https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/655733

https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/640126

While the Indexer can be resource intensive at times for large projects, the slowdowns reported are unusually bad. We are investigating the issue but have not had much luck reproducing them. Hence, we would like more data from customers who are experiencing this issue. 

We like to ask people experiencing this issue to generate thread stack dumps when the hang/slowdown happens.

The easiest way to do that:

Windows:

  1. Launch CCS from command window using the command “<CCS INSTALL DIR>/ccsv[x]/eclipse/ccstudio –debug”.
  2. This would launch CCS, and also open a second command window – in this second command window, right-click on the window header, select Properties, and increase the Screen Buffer Size to 200 x 5000 (w x h).  It is also helpful to increase the Window Size to 200 x 70 (w x h).
  3. Now when the hang/slowdown occurs, the user should bring the second command window into focus, and click Ctrl + Pause/Break a few times.  Each time it would generate a full thread stack dump.  That would need to be captured into a text file.

Linux:

  1. Launch CCS from terminal window using the command “<CCS INSTALL DIR>/ccsv[x]/eclipse/ccstudio”.
  2. Now, reproduce the hang/slowdown. Once it occurs, use the "ps" or the "jps" command to find out the process id (pid) of the Java VM.
  3. Invoke "kill -3 <pid>" where <pid> is the process id of the Java VM.
  4. A thread dump will be printed on the console where you started Eclipse.  It would be best to repeat the "kill" command a few times.

Please zip the text file and attach it to this thread (or your thread if you created one on the forum for your issue)

If you are really slowed down, you can disable the Indexer as a workaround. But note that you will then lose some advanced editor features (i.e. Jump to declaration, etc..)

UPDATE: After analysis of some logs, one bug was identified and fixed (CCDSK-3103). The fix will be available in CCSv8.1. A patch for 8.0 is available if you wish to try it. See:

https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/675866/2489974#2489974

Thanks

ki