Hi

Sometimes when debugging this particular piece of software
from within Visual Studio 2005, the program being debugged
suddently stops responding and starts pulling a 100% CPU load.
The problem most often occurs when stepping through the code - I
press the F10 but control is not given back to VS for about
1-5 minutes. In the mean time the process being debugged
pulls all available clock cycles.

By inspecting the process from SysInternals Process Explorer, I
find that 3-4 threads are going through 80.000 - 100.000 context
switches pr. second. According to their call stacks, they are
all stuck within:

 mscorwks.dll!CertCreateAuthenticodeLicense+0x30b8c

I have no idea what this is. The entry functions for the
troublesome threads are one of:

 RpcBCacheFree
 InitializeFusion

I don't known these either, and google give me nothing. Its all
rather confusing, and the fact that VS looses contact with the
process being debugged leads me to suspect that it all has something
to do with the communication between the process and the debugger.

The problem is experienced on both VS2005 Beta2, RC1, and the 180
day trial of Team System. It is experienced on multiple machines,
but never outside the debugger.

Any help on the subject is appreciated.

/holmgren