Ralf,
We are a bit lost on this particular issue; if you have the time, a few logs could help get additional insights (as suggested by some developers).
A Debug Server log might help (menu Help --> CCS Support --> enable and define a filename for the field Debug Server Log). It sounds like there’s a thread that is created on every Debug Server launch and that thread is stuck in a loop which never terminates. This is unlikely to be directly debugger related as the debugger usually only uses one thread. The debugger log might capture suspicious activity that could point a finger, but it isn’t likely.
I think a more useful thing would be a Java thread dump. I’ve never done this before, but check the instructions below:
Java thread dumps
- Open DOS Command window and navigate to CCSInstallRoot\ccsv#\eclipse
- Start CCS by typing “eclipsec --launcher.ini ccstudio.ini > javadumps.log” in command-window.
- Then, when the deadlock happens or java thread dump should be captured, place focus on the command-window, and hit Ctrl+Break. The thread dump is now in eclipse/ javadumps.log.
One third detail I was thinking that may help is increase the heap memory used by CCS (edit the file <CCS_INSTALL_DIR>/ccsv5/eclipse/ccstudio.ini and change the option -Xmx384m to something higher such as 512m or 768m). This would be more a workaround than a real fix, but if nothing else helps it may be worth trying.
Hope this helps,
Rafael