Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<fdb072ec0409170658344931d5@mail.gmail.com>
Date:	Fri, 17 Sep 2004 09:58:37 -0400
From:	Robert Pendell <shinji257 AT gmail DOT com>
Reply-To:	Robert Pendell <shinji257 AT gmail DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Cygwin processes getting stuck on max CPU usage; XP SP2 problem?
In-Reply-To:	<414A70F8.A84FAADF@dessent.net>
Mime-Version:	1.0
References:	<414A5C34 DOT 9050305 AT nc DOT rr DOT com> <414A70F8 DOT A84FAADF AT dessent DOT net>
X-IsSubscribed:	yes

Oh and csrss.exe isn't anything new with XP SP2.  It is on SP1 as well.


On Thu, 16 Sep 2004 22:07:04 -0700, Brian Dessent <brian AT dessent DOT net> wrote:
> Joe Krahn wrote:
> >
> > I use SysInternal's Process Explorer a lot. After
> > installing XP SP2, if I browse Cygwin processes in
> > ProceExp, I can no longer get the list of loaded
> > DLLs, and they get stuck at max CPU usage along
> > with csrss.exe.
> >
> > The CygWin processes continue working OK, but the
> > whole system (obviously) gets slowed down.
> >
> > I noticed that csrss.exe is new with XP SP2.
> > Maybe it's involved in querying process information,
> > and does not play well with CygWin?
> 
> This is a reported issue and it has to do with the way Process Explorer
> works.  It attaches a thread to the target process in order to list the
> modules, and cygwin processes don't like this for some reason.  It
> started in the early 1.5 days, and is nothing really that new.
> 
> If you have symbols installed and you list the threads for the hung
> Cygwin process you'll see the stuck one is in a loop in
> ntdll.dll!RtlConvertUiListToApiList, as well as a corresponding thread
> in csrss.exe (CSRSRV.dll!ValidateMessageString) for each.  The CPU usage
> seems to be split equally between them all.
> 
> So, it's definitely an interaction between Cygwin and Process Explorer's
> grubby little fingers... however no one seems to be interestd in fixing
> it so for the time being the solution seems to be "Don't accidently
> enable the 'DLLs View' of a cygwin process in ProcExp."
> 
> Brian
> 
> 
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Problem reports:       http://cygwin.com/problems.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 
> 



-- 
Robert Pendell
shinji257 AT gmail DOT com

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -