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
Date:	Thu, 23 Sep 2004 21:07:57 +0100 (GMT Daylight Time)
From:	Simon Barnes <simon DOT barnes AT london DOT oilfield DOT slb DOT com>
Subject:	Re: Cygwin processes getting stuck on max CPU usage; XP SP2 problem?
X-X-Sender:	barnes AT hydra DOT gatwick DOT eur DOT slb DOT com
To:	cygwin AT cygwin DOT com
Message-id:	<Pine.WNT.4.58.0409232101080.2332@3MWVC01-WGG.eur.slb.com>
MIME-version:	1.0
X-AntiVirus:	Sophos nammta01

Some of my colleagues and I are seeing this without using Process
Explorer.  No doubt some other automated process is triggering it, but we
don't know which.

Is there anything I can do to help work towards a fix?  It's moderately
inconvenient having to restart rxvt or bash every few hours.

Simon


> 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."


--
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 -