• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 80 subscribers
  • Views 1009 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 PROBLEM : GOES TO INFINITE LOOP

Srikant Avasarala
Prodigy 110 points


Hi ,

Sometimes while debugging , the CCS ges into infinite loop i.e. the process pop up window remains for a very long time and does not proceed to the run time.... and I have to manually open the task manager and kill the application. But after doing that , when I open CCS again , I cannot choose the same workspace . It says that the workspace cannot be opened and I have to create a new workspace . However , after I restart my computer , I can open the same workspace again...

Why is this happening? And how should I overcome this .... I dont want to end up having a lot of workspace areas and want to continue in the same workspace ....

Thanks

Srikant

  • 0
    Expert 1725 points

    I had similar problems last year.  When you use task manager to kill CCS it doesn't always take out all the components so part of it is still running, thinking the workspace is in use.  If you hunt through the process list you might be able to find the extra component you need to terminate (I can't remember what it was called...perhaps eclipse.exe or something related to java...?), then you will be able to open your workspace again.  To be safe perhaps have a dry run first: open CCS and monitor the process list to spot which processes are started, then close it normally and see which ones go away, then try again this time terminating the application in task manager and see which processes are still hanging on - this way you'll know what to look for next time it crashes.  But be cautious - don't go randomly terminating processes and then blame me when the computer crashes!!!

    My CCS used to lock up when trying to download or connect to the msp device.  I have found that simply disconnecting the debugger from the PC (I use a USB FET430UIF) is a much better solution as it normally causes CCS to exit the busy loop and start responding again.  Then I plug the debugger back in and it normally works ok (for a while at least!).  This is far quicker (and safer) than terminating CCS and then trying to kill the workspace or restart the PC so I recommend trying this first!

  • 0 in reply to chris_m
    Guru 227245 points

    chris_m said:
    perhaps eclipse.exe or something related to java...?)

    Possible. CCS is based on Eclipse and Exlipse is running on Java.

    It's possible that parts of the workspace are still opened by the application for exclusive access, so a new instance cannot open the file(s). THis often happens if you kill an applicaiton that still has a file open for writing/modifying (such as the config file).

    There is an applicaitonf or WIndows, called 'unlocker', which runs in debug mode. Whenever you have a problem deleting a file because it is still opened by an application (even if the application already died), it automatically starts and asks you whether to untie the file from the app, or delete/rename it directly. It can also be called from explorer on a specific file to unlock it. It even offers to add the file to the Windows startup processing, so you can act on files which are always opened by the system (uncluding some virus files), and the file will be removed or renamed on next system startup before anything else is loaded that can lock the file down again.

    Java in particular has a habit of leavign things in an undesireable state if something crashes. I use Azureus, a Java-based filesharing program. It starts a backgrounf  'ping' process for load balancing. If Azureus crashes, the ping process is not killed too, and one cannot restart the application as long as this old process is still running.

**Attention** This is a public forum