X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 06E1C3858298
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1671717356;
	bh=s3bcgU312VxoyuFqI/iqAcbNZsZyAH4cqSDjBem6CkE=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	From;
	b=rHzu6BjPNDNjvor9desTEK6YWFHvSpeuB8WOrz8YN5jERBvd/VkVynSzha4PkaGuw
	/2F5Y2kl7VeMKKgGNWIeCCPLMVYbUU5eoTR5SWrr1bG9TV3LA8a+iWwHWsOF7bisec
	cGYmcZFQ4ecACHbSpIFnE3uz8iCuMVz1sefzvpKw=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.1 sourceware.org 99ED23858D1E
DKIM-Filter:	OpenDKIM Filter v2.10.3 conssluserg-01.nifty.com 2BMDsjLP031129
X-Nifty-SrcIP:	[220.150.135.41]
Date:	Thu, 22 Dec 2022 22:54:45 +0900
To:	cygwin AT cygwin DOT com
Subject:	Re: Resizing window while showing git log locks up Command Line
Message-Id:	<20221222225445.359b688e8403e85f3ea9ebc6@nifty.ne.jp>
In-Reply-To:	<20221222181728.89ffee4e52192f270ccbef5a@nifty.ne.jp>
References:	<CH2PR17MB392731321A3A24CC6FCC2A9CC1EB9 AT CH2PR17MB3927 DOT namprd17 DOT prod DOT outlook DOT com>
	<CA+kUOanYkNMXNvcUaX5sUX+nmbAU3erNvJ-WD3YTaN8ccdsTDQ AT mail DOT gmail DOT com>
	<20221222181728 DOT 89ffee4e52192f270ccbef5a AT nifty DOT ne DOT jp>
X-Mailer:	Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
Mime-Version:	1.0
X-Spam-Status:	No, score=-5.1 required=5.0 tests=BAYES_00, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_NONE,
	SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.6
X-Spam-Checker-Version:	SpamAssassin 3.4.6 (2021-04-09) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Takashi Yano via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
Errors-To:	cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

On Thu, 22 Dec 2022 18:17:28 +0900
Takashi Yano wrote:
> On Wed, 21 Dec 2022 21:30:35 +0000
> Adam Dinwoodie wrote:
> > On Wed, 21 Dec 2022 at 16:08, Gregory Mason via Cygwin wrote:
> > >
> > > Hello Cygwin volunteers,
> > >
> > > I was asked to forward this bug report from the git-for-windows bug report: https://github.com/git-for-windows/git/issues/4060
> > > Original bug report from garretwilson
> > >
> > > > Find a Git repository with a long commit history.
> > > > Enter `git log`
> > > > Git will show the log history and wait for you to page through the history or hit q to exit.
> > > > Press Win+Left-Arrow to snap the window to the left side of the screen.
> > > > The window is now hung. Nothing can be typed to get it un-hung. Typing q does nothing. Typing Ctrl+C does nothing. Typing <Enter> does nothing. > The only way out of this is to close the terminal window and start a new Command Prompt or PowerShell session.
> > > >
> > > > I've reproduced this with Command Line and with PowerShell 7.2.6.
> > >
> > > I am also experiencing this issue with the following setup:
> > > CYGWIN_NT-10.0-19044 version 3.4.3-1.x86_64 (runneradmin AT fv-az479-541) (gcc version 11.3.0 (GCC) ) 2022-12-16 12:38 UTC
> > >
> > > Windows 10
> > > Version 21H2
> > > Installed on    ?7/?11/?2022
> > > OS build        19044.2251
> > > Experience      Windows Feature Experience Pack 120.2212.4180.0
> > >
> > > If you need further information, please let me know.
> > 
> > This looks like it's an issue with less, which will be the pager that
> > Git is using. I've just verified I can reproduce it by running
> > `C:\cygwin64\bin\less.exe C:\cygwin64\var\log\setup.log` from within a
> > PowerShell terminal, then resizing the terminal; it doesn't need to be
> > a "snap" to trigger the behaviour.
> > 
> > Somewhat to my surprise, `more` and `vim` don't exhibit this behaviour.
> 
> Thanks for the report. I looked into this problem, and found
> the cause. less uses longjmp in signal handler, and if signal
> handler is called while cygwin acquiring the mutex, the mutex
> will not be released. This causes deadlock.
> 
> I will submit a patch for this issue shortly.

Now test release with this patch is ready.
Please test cygwin 3.5.0-0.63.gf6e4e98d3071 (Test).

https://cygwin.com/faq.html#faq.setup.testrels

-- 
Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>

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

- Raw text -