X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:message-id:in-reply-to:references
	:subject:mime-version:content-type:content-transfer-encoding; q=
	dns; s=default; b=Q99LWiCCiRPfiludfr1+unicxy1lCQEXR9Yh58WNwTy0Fk
	p4DvqgHx0svzgSE8EnC5VV6+pjfEB+qsWX3uYxlhwLlPSHr/A03aRVu8Pj/RRHpg
	6sB6j8lExy/15MeT5ZVhwq0ENYQ0k5CI/kuVLEUEkURyat2nL4p1uV9ZWYSxQ=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:message-id:in-reply-to:references
	:subject:mime-version:content-type:content-transfer-encoding; s=
	default; bh=XvscgKK3h9QYvJfl/C4hFmSWRHQ=; b=kt+0KTSD6Buw1xnCya3Y
	wMFCNk7wQVc7q3+h0JQ1cW6WrFZDYFrCpnwI3oDojoY1Ap94HvWG5x1gw9Gfm5G2
	7dLEoGT9xMbtbmHGSM09e/6jPDnyiG4vKGz3+f+CGCZDpmSekHQrKxx6gddNPMb1
	Y+OMmUiCITOqk6MteSJn678=
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
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=2.7 required=5.0 tests=BAYES_50,SPF_HELO_PASS,SPF_NEUTRAL,URI_HEX autolearn=no version=3.3.2 spammy=corporate, Mintty, Exit, H*F:U*cygwin
X-HELO: n5.nabble.com
Date: Fri, 3 Nov 2017 13:02:28 -0700 (MST)
From: Rick Maus <cygwin AT mausit DOT com>
To: cygwin AT cygwin DOT com
Message-ID: <1509739348682-0.post@n5.nabble.com>
In-Reply-To: <CAAARkvL38n1yJi=HzVryOSt=ybb7hNT71miahswT_FLAjAwcJw@mail.gmail.com>
References: <CAAARkvKRkbruuFyfOJd1qQvFT52oZSSGMKJczr6JtgokrWCHNg AT mail DOT gmail DOT com> <CAAARkvJtysj_s-N848_HznfO2N+iWP5bAntjOznbNq4mggmCbA AT mail DOT gmail DOT com> <CAAARkvL5YkBrjRDBfbOAdPiAfW5M1+DJnqsCQX+hBf9UVjcZ9w AT mail DOT gmail DOT com> <CAAARkvLSMOfThqGpiniYP_5wnc5mBLDeCua6da2skREKhGwGjw AT mail DOT gmail DOT com> <CAAARkvL38n1yJi=HzVryOSt=ybb7hNT71miahswT_FLAjAwcJw AT mail DOT gmail DOT com>
Subject: Re: Mintty Crash on Exit after SSH on Windows 10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I am experiencing a similar situation on a recently reimaged Windows 10
computer in a large corporate environment, namely:

* Either typing "exit" or clicking the Windows close [X] button from a
Cygwin bash terminal (mintty under the hood) results in the process hanging
with it either eventually closing after a few minutes (or) Windows
indicating the process is not responding and offering to terminate it.
* Moving my home directory out of the way and recreating a basic home
directory did NOT work around the situation for me which is different than
the experience Bryan Tong described.

I have noticed that our organization is intentionally slower to roll out
Windows updates to our environment, so I am keeping my fingers crossed for
that situation.  If anyone wants a thread dump to investigate, please feel
free to reach out.



--
Sent from: http://cygwin.1069669.n5.nabble.com/Cygwin-list-f3.html

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