From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 104460 invoked by alias); 20 Aug 2015 22:21:32 -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 104450 invoked by uid 89); 20 Aug 2015 22:21:31 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=2.4 required=5.0 tests=AWL,BAYES_50,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-ig0-f178.google.com Received: from mail-ig0-f178.google.com (HELO mail-ig0-f178.google.com) (209.85.213.178) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Thu, 20 Aug 2015 22:21:30 +0000 Received: by igfj19 with SMTP id j19so5265465igf.0 for ; Thu, 20 Aug 2015 15:21:28 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.50.64.212 with SMTP id q20mr334434igs.5.1440109287899; Thu, 20 Aug 2015 15:21:27 -0700 (PDT) Received: by 10.107.63.4 with HTTP; Thu, 20 Aug 2015 15:21:27 -0700 (PDT) In-Reply-To: <26A19798-1F20-4D52-A311-C8312E0D4621@etr-usa.com> References: <26A19798-1F20-4D52-A311-C8312E0D4621@etr-usa.com> Date: Thu, 20 Aug 2015 22:21:00 -0000 Message-ID: Subject: Re: Some programs (vi, ssh) crash when screen buffer height is big From: Sous Lesquels To: cygwin@cygwin.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2015-08/txt/msg00351.txt.bz2 Thanks Warren. > Actually, it did here. I see it separate, at least in a Web browser: - This thread: https://cygwin.com/ml/cygwin/2015-08/threads.html#00347 - The original thread I tried to reply to: https://cygwin.com/ml/cygwin/2014-07/threads.html#00185 My intention was to reply to this message: https://cygwin.com/ml/cygwin/2014-07/msg00191.html > You are aware that Microsoft is giving out free Windows 10 upgrades to va= lid Windows 7 license holders, right? Yeah - however, wanted to test under relatively same conditions considering what I use daily and I don't decide when to get the upgrade here... > but also because I continue to be unable to reproduce your symptom under = Windows 10 Just to confirm - you did set the params of cmd.exe one to this: Screen Buffer Size: 208w 9999h Window Size: 208w 69h the files you headed have long lines and you are using 64bit Cygwin? Those two seem really important. I did not have issues with 32bit. I seem not to have issues with smaller windows / buffer sizes. I also don't seem to be able to reproduce when files have short lines. > I=E2=80=99ve also failed to reproduce your symptom under MinTTY I cannot reproduce under mintty either. > (You can make the test script time(1)-able by adding =E2=80=9C-c q=E2=80= =9D to the vim command, so that it immediately quits after loading the log = file.) Nah, not needed that much - it crashes itself most of the time :) > When you say =E2=80=9Ccompletely fresh=E2=80=A6Cygwin=E2=80=9D, do you me= an that you didn=E2=80=99t even start with an archive of downloaded package= s? Yep - I basically had a fresh Win 7 and used internet to download all thing= s. > Did you use a different package mirror? Yes - I can try with the same mirror if you think that would make a difference. Given that I am constantly (as in - 20 times a day at least) reproducing this on three different machines, different versions of Cygwin (I likely updated it a few times since last year), etc., I would say that's not very likely a cause. > I don=E2=80=99t know if this is relevant, but have you done a memtest86 (= or similar) pass on that machine? Dodgy RAM could explain intermittent cal= loc() failures. It's actually two different machines. One is physical and one a VM on a totally different physical machine. I also tried it on a third VM (which is on a third physical machine). It should not be machine related. Note that I get a lot of different behaviors, here are some: - cmalloc would have returned NULL that you referenced - Garbage on screen - e.g. my PS1 has some ANSI color escape codes and they look not to be interpreted when it goes into this state. I have: PS1=3D\[\e[31m\] and instead of making text red, it actually prints [31m - Mixed text - e.g. I scroll a line in vim (but happens also with less, cat, etc.) and it doesn't clear the screen completely, i.e. mixes old and new contents - Segfaults It's very interesting that only I can reproduce. Cannot pinpoint what can be the difference between the envs... :( -- 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