Occasionally when returning to Visual Studio 2003 that has been idle for a few hours the CPU starts to spin and End Process is the only solution. I have included the stack trace of the offending thread. This problem occurs 1-2 a week and when it does occur I have 2-3 instances of vs2003 running, but only the 1 instance goes bad.
Currently whole tomato is the only plug-in I have installed. The problem only seems to happen when whole tomato is installed. Unfortunately it is not consistent, so debugging it will be a challenge to say the least. Let me know if there is anything else I can do to help solve this.
I'm having a similar problem, although (at least on my machine) it doesn't seem related to the amount of time VS.NET2003 has been open. Also, on my machine, it sometimes recovers after crunching away for 5 minutes or so. I tried capturing the callstack periodically while the devenv.exe process is seemingly locked at 100% usage, and the last node is always the same. While the stack can be varying lengths, MigrateDevColor from the va_x.dll always seems to be the last node (presumably the problem is in this function?):