X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 	tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <5195c8761001180252i6afffb3m4aa0a9d9fea85580@mail.gmail.com>
References: <5195c8761001180247sb63f867sfaf1696c3b9a21ca AT mail DOT gmail DOT com> 	 <5195c8761001180252i6afffb3m4aa0a9d9fea85580 AT mail DOT gmail DOT com>
Date: Tue, 19 Jan 2010 07:35:53 +1300
Message-ID: <db95995b1001181035h6cd83cc0x6502a75f5a936d4a@mail.gmail.com>
Subject: Re: Gitk issue post 1.7.1 upgrade
From: David Antliff <david DOT antliff AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=ISO-8859-1
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Mon, Jan 18, 2010 at 23:52, Jeenu V <jeenuv AT gmail DOT com> wrote:
> I'm using Gitk from Cygwin and I come across this problem quite
> frequently post upgrade to 1.7.1. While I'm viewing commits a pop-up
> appears saying "writing to stdout fails". I'm able to consistently
> reproduce it by making quick random clicks on the commit graph. And I
> don't remember seeing this behavior pre-1.7.1 Cygwin.
>
> I've captured log and is attached. Has any one else come across this?

I've seen this a lot, and at the time I thought it might be related to
clicking on a commit that contains a file that no longer exists in the
working tree. Throughout some of our repositories we had 'mass
renaming' commits, and I have noticed that it seems to happen quite
often if I quickly click commits on the far side of such a commit.

That said, it didn't seem particularly consistent and I am not able to
definitely point at that as a cause. It has the feel of a race
condition.

I don't see it happen in Linux at all.

I've also seen gitk on 1.7.1 Cygwin become intolerably slow within
seconds of opening within a (very small, < 10 commits) repository with
many renames in it. This caused us to rebuild the repository again,
only to see the same problem. But I'm not sure if this is related.

-- David.

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