X-Spam-Check-By: sourceware.org
Message-ID: <4495D125.4693156F@dessent.net>
Date: Sun, 18 Jun 2006 15:18:13 -0700
From: Brian Dessent <brian AT dessent DOT net>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
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> <4495C806 DOT 2020805 AT tlinx DOT org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
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

Linda Walsh wrote:

>     I didn't see Science Guy mention procexp?  Um, hey, S.G.,
> are you using Process Explorer?

There are probably other programs that use the same technique and cause
the same effect, like windows update.

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

No, the problem was never fixed on ProcExp's end.  Believe me, I use
both Cygwin and ProcExp every day, and this was always broken until
Linbox sponsored cgf to look into it and create a fix, which only
happened last month.

http://cygwin.com/ml/cygwin/2006-05/msg00525.html
http://cygwin.com/ml/cygwin-cvs/2006-q2/msg00123.html

(I think that was the one that actually fixed the problem, but it might
have been http://cygwin.com/ml/cygwin-cvs/2006-q2/msg00121.html)

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

The last release of Cygwin was 1.5.19-4 on 2006-01-20, so unless you
have a time machine, a fix made on 2006-05-17 will not be included. 
Besides, using the latest snapshot should always be the first thing you
try when encountering a problem before reporting it to the list.  Nobody
cares about hearing about bugs that have already been fixed.

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/