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:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=jz
	0e0QoIoGMm7T/Qk0TU4wmV9T8azWj1ZyMj6Gju1Cv9TE13wZWjWFiwLyhMq8vt06
	S0lAMo2JYG7oLgZJCGY1lUEcbR/UkVed6TBkBCU5jKRVoiFwdXzD/AnkcSOnm8fm
	KUHeLLQDA+E2t7d4KOyi1wGUKUQPF+en8nY1PaDxE=
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:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; s=default; bh=zgjytlEC
	QAv3jEvnxEhVHGF7N10=; b=USLBzqvI+FgHrCtxl0ezCX/mYPyU+lqpkGosnU7m
	uaQvnIn8MJ7hUVtFQX+ENSg3chYbKAgRaVzs+U8tPIh6tPfvQqNp25t6XM9b0kPo
	o5VVxYiFvOXes/iVUbhMn9hf9WWcHrJir/rlQLzMnkxN73pH3jTLlbciNJqSt1ze
	eQU=
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=1.8 required=5.0 tests=AWL,BAYES_40,RCVD_IN_DNSWL_LOW,SPF_PASS,URIBL_SBL autolearn=ham version=3.3.2
X-HELO:	mail-io0-f176.google.com
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=eMAe81PtKBwMXNk/E4NrzPX1epNCmW5812L5/1zIjKY=; b=N3URnXWyZJbd/Zjz7s6gqSLWhnGOEOId7ApEVDcPeVFUhbWV+7rzd2hkVgH64h1Tgr fUnBaGIXH3YqW6bsY6fsv7C3RWA3miqe5RR4F/0+ljFDdMIWxiXk4ugSYGB3k9xmyfVm vJ2Jc4gvJ4oMLVEvmXtbG1TrzcrZk9c8W74MYb6hlQvcLYcB+53IRjzAbkiTG6YGkLcg 3hFoH/CWQS8rB51kMle8IYURHtqH7WRAFMDeQSqoKf6aTRuvzE0Ia+vSV6Zs65S+p2/4 i9x2lcgvKg5BM8+ZN2hrgjzYpFAJ+x7NZ9R5rVB8Il2ypr1ORlTH1EmVcEPYkWquoXRr Lblg==
X-Gm-Message-State:	ALoCoQm8gbYWKWpADH14wPXPgJZq9OTtsWf8jcwBdP0pQwFbQHmLv8yt3LJNJ/+pWn/4amWNapuW
MIME-Version:	1.0
X-Received:	by 10.107.6.209 with SMTP id f78mr2718324ioi.194.1443589838507; Tue, 29 Sep 2015 22:10:38 -0700 (PDT)
In-Reply-To:	<CAAARkvKRkbruuFyfOJd1qQvFT52oZSSGMKJczr6JtgokrWCHNg@mail.gmail.com>
References:	<CAAARkvKRkbruuFyfOJd1qQvFT52oZSSGMKJczr6JtgokrWCHNg AT mail DOT gmail DOT com>
Date:	Tue, 29 Sep 2015 23:10:38 -0600
Message-ID:	<CAAARkvJtysj_s-N848_HznfO2N+iWP5bAntjOznbNq4mggmCbA@mail.gmail.com>
Subject:	Re: Mintty Crash on Exit after SSH on Windows 10
From:	Bryan Tong <contact AT nullivex DOT com>
To:	cygwin AT cygwin DOT com

I wasnt able to get any of the replies however I saw them on the mailing list.

First of all, yes the problems continue if I type "exit" into each windows.

Also happens if I just press the "X" on the window.

Enter, doesnt do anything on the window. I have to either wait about
60 seconds for the window to exit after claiming to not respond or I
have to use the task manager to kill it.

I am trying the others now and will let you know.

What I can tell you is that I just did a fresh install of cygwin
32bit. I install nano, vim, ssh, ping as well was the base package
set.

The problem continues on that installation as well.

On Thu, Sep 17, 2015 at 2:10 AM, Bryan Tong <contact AT nullivex DOT com> wrote:
> Hello,
>
> I recently upgraded to Windows 10 and ever since I have I am getting a
> hang every time I try to exit a Mintty window after using SSH.
>
> What makes this issue more interesting is that I cant always reproduce
> it. It only happens after I have long standing SSH sessions.
>
> After I press "CTL + a + d" the final time when I am back at the
> cygwin login prompt. The window hangs and my cursor disappears when I
> try to mouse into the window (this includes the title bar, an exit
> buttons). At this point the only option is killing from the task
> manager or waiting about a minute until the window dies.
>
> I am thinking this has to do with unclosed sockets after I have done a
> bunch of googling on what might be causing this.
>
> There is one mailing thread pertaining to a similar issue but it
> doesnt match up  exactly.
>
> It definitely started directly after the upgrade to Windows 10. I did
> not upgrade cygwin until after I ran into this problem. However the
> issue still persists after the upgrade. I believe I am running the
> latest versions.
>
> I have attached my cygcheck to help.
>
> Best way to reproduce
>
> 1) Open mintty
> 2) ssh to a host
> 3) idle on this host for say 5 minutes
> 4) press "ctl + a + d" to disconnect from the host
> 5) press "ctl + a + d" to disconnect from the Mintty window
>
> I can almost always reproduce this after working on remote servers.
> However when I try to do it on command it happen every time.
>
> I want to point out that I am also using this SSH option.
>
> ServerAliveInterval 30
>
> I am starting to wonder if maybe that option is causing SSH to keep
> the window open as it tries to keep the server alive. It seems that
> the 30 second window is close to how long I am seeing these windows
> hang open.
>
> I am not even sure where to look for more debugging. I am more curious
> if anyone else is experiencing this?
>
> Please note that I upgraded my Desktops from Windows 7 -> Windows 10
> and they both see the problem. On the other hand my laptop I upgraded
> from Windows 8 -> Windows 10 and it continues to work normally.
>
> Any help would be appreciated I am stumped on this one.
>
> Thanks
>
> --
> eSited LLC
> (701) 390-9638



-- 
eSited LLC
(701) 390-9638

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