From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18653 invoked by alias); 30 Sep 2015 05:10:47 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 18632 invoked by uid 89); 30 Sep 2015 05:10:42 -0000 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 Received: from mail-io0-f176.google.com (HELO mail-io0-f176.google.com) (209.85.223.176) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Wed, 30 Sep 2015 05:10:40 +0000 Received: by ioiz6 with SMTP id z6so35189521ioi.2 for ; Tue, 29 Sep 2015 22:10:38 -0700 (PDT) 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) Received: by 10.36.5.147 with HTTP; Tue, 29 Sep 2015 22:10:38 -0700 (PDT) In-Reply-To: References: Date: Wed, 30 Sep 2015 05:10:00 -0000 Message-ID: Subject: Re: Mintty Crash on Exit after SSH on Windows 10 From: Bryan Tong To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 X-SW-Source: 2015-09/txt/msg00510.txt.bz2 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 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