Process Explorer (was: startx hanging - startup problem located)

[martouf .]

"Brian Dessent" wrote:
> Specifically, if you click on the Threads tab of the Properties page of a process,
> ProcExp attaches its own thread to the process and this causes the Cygwin
> process to consume 100% cpu. 

yes, bringing up the Threads tab on processes like 'xterm' and 'sh'
causes a new thread "ntdll.dll!RtlConvertUiListToApiList+0xNNN" to be
created.  It is simple to remedy this by killing the thread.  Having
done so, CPU usage returns to normal and the Cygwin process becomes
responsive again.