I have a simple console test application that sets up a TCP channel for
remoting and registers an object, and then services requests until I close
it. I've compiled it to target .net 1.1 and 2.0. The problem is that after
a while, in the .net 2.0 version, a thread makes a native API call to
RtlConvertUiListToApiList and will begin to hog the spare cycles of the CPU.
This doesn't happen when the .net 1.1 version runs. I can also initiate the
problem by opening Process Explorer from sysinternals and view the process's
thread properties. I don't have any documentation on the native API and I
can't tell from the stack traces on that thread what is happening. Other
than this behavior, my app works okay. I don't think I'm doing anything
unusual.

Please disregard this. This seems to be a bug in Process Explorer. The
behavior will appear on any sort of application.

"silent tone" wrote: