X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
Date:	Thu, 11 Mar 2010 20:39:02 +0000
Message-ID:	<416096c61003111239m60a2a2f1i999000640b108e6e@mail.gmail.com>
Subject:	mintty 0.6-beta3 problem (was: Re: Close==SIGHUP)
From:	Andy Koppe <andy DOT koppe AT gmail DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
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

Reini Urban:
> Looks like 6-beta3 is not good.
>
> Two mintty sessions with just bash doing nothing keep the CPU busy with 50%
> per bash, so that I even cannot successfully open a google chrome url.

Thanks. This won't be to do with the Close==SIGHUP thing, since that's
not in beta3. And of course I need more detail:
- What Cygwin and Windows versions are you running?
- How did you start the mintty instances?
- Does the issue occur straight away or was there something that might
have triggered it?
- Is it the mintty or the bash processes that occupy the CPU?

Perhaps we should take this to the mintty issue tracker, since the
beta isn't shipped with Cygwin.

Andy

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

- Raw text -