X-Spam-Check-By:	sourceware.org
Message-ID:	<4495C806.2020805@tlinx.org>
Date:	Sun, 18 Jun 2006 14:39:18 -0700
From:	Linda Walsh <cygwin AT tlinx DOT org>
User-Agent:	Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: bash and CSRSS consuming 100% of CPU
References:	<002401c690e2$6f2656b0$0a3b6080 AT joehome> <449208C4 DOT 4CF28807 AT dessent DOT net>
In-Reply-To:	<449208C4.4CF28807@dessent.net>
X-IsSubscribed:	yes
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

Brian Dessent wrote:
> Science Guy wrote:
>   
>> This problem has been noted before by someone else,
>>
>> http://www.mail-archive.com/cygwin AT cygwin DOT com/msg37532.html
>>
>> but I followed the threads and can find no resolution. 
>>     

>> When I fire-up a cygwin bash window, everything is fine for a few minutes.
>> Then the CPU utilization on my system suddenly jumps to 100%.  Bash is
>> typically grabbing about 80% of the CPU, with almost all the rest grabbed by
>> CSRSS. 
>>     
>
> The problem is caused by sysinternals' process explorer injecting its
> own threads into other processes.  It was also fixed several months ago
> in cygwin.  Try a snapshot.
>   
====
    I didn't see Science Guy mention procexp?  Um, hey, S.G.,
are you using Process Explorer?

    I remember the ProcExp bug, but it only happened when I tried to
show properties on a cygwin process.  I believe Mark released a
followup version within 2 weeks that fixed the bug.  It wasn't a
cygwin bug (at least not the one I'm thinking of).

    But... hey, SG, if you are using Procexp, have you tried
getting an recent version?

    Brian -- not sure I understand: some other program injects code
into the cygwin process and it's a cygwin bug that should be fixed by
a new snapshot? 

    Also, if it was fixed several months ago, would he need a snapshot:
are the snapshots that out of sync with the released version?

linda


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