From: Rick Maus <cygwin@mausit.com>
To: cygwin@cygwin.com
Subject: Re: Mintty Crash on Exit after SSH on Windows 10
Date: Fri, 03 Nov 2017 20:02:00 -0000 [thread overview]
Message-ID: <1509739348682-0.post@n5.nabble.com> (raw)
In-Reply-To: <CAAARkvL38n1yJi=HzVryOSt=ybb7hNT71miahswT_FLAjAwcJw@mail.gmail.com>
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
next prev parent reply other threads:[~2017-11-03 20:02 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 ` Mintty Crash " Bryan Tong
2015-09-30 5:15 ` Bryan Tong
2015-09-30 5:21 ` Bryan Tong
2015-11-21 1:19 ` Bryan Tong
2017-11-03 20:02 ` Rick Maus [this message]
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=1509739348682-0.post@n5.nabble.com \
--to=cygwin@mausit.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).