From: Bryan Tong <contact@nullivex.com>
To: cygwin@cygwin.com
Subject: Re: Mintty Crash on Exit after SSH on Windows 10
Date: Wed, 30 Sep 2015 05:10:00 -0000 [thread overview]
Message-ID: <CAAARkvJtysj_s-N848_HznfO2N+iWP5bAntjOznbNq4mggmCbA@mail.gmail.com> (raw)
In-Reply-To: <CAAARkvKRkbruuFyfOJd1qQvFT52oZSSGMKJczr6JtgokrWCHNg@mail.gmail.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@nullivex.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
next prev parent reply other threads:[~2015-09-30 5:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-17 8:10 Bryan Tong
2015-09-17 10:14 ` Marco Atzeri
2015-09-17 21:05 ` Mintty Hang " Thomas Wolff
2015-09-17 21:36 ` Warren Young
2015-09-30 5:10 ` Bryan Tong [this message]
2015-09-30 5:15 ` Mintty Crash " Bryan Tong
2015-09-30 5:21 ` Bryan Tong
2015-11-21 1:19 ` Bryan Tong
2017-11-03 20:02 ` Rick Maus
2018-04-23 15:48 ` cyg
2018-04-23 17:38 ` Thomas Wolff
2015-09-30 8:54 ` Thomas Wolff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAARkvJtysj_s-N848_HznfO2N+iWP5bAntjOznbNq4mggmCbA@mail.gmail.com \
--to=contact@nullivex.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).