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
	:content-transfer-encoding; q=dns; s=default; b=LGS/boQYM4hK++ss
	7vHcFJpntjxmk4LIozwVaL3Su0tliOTF5RzGZjFcgJ3coZ1RfoMaOeSjB6h5QMTX
	ueoCDQQ1Wqy9mo7ydj0k1C91sOhInqjJm0lKTYxoS01XYVC3aQ1DMyMAfHYZ2dVF
	4sBUOByKtYWKcKNqedrq+K3heNc=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
MIME-Version: 1.0
In-Reply-To: <26A19798-1F20-4D52-A311-C8312E0D4621@etr-usa.com>
References: <CAHV8iDH4pG0FoGrckc36atQUV+SWOnryJ-zBDK92HTGgPRC=Ew AT mail DOT gmail DOT com>	<26A19798-1F20-4D52-A311-C8312E0D4621 AT etr-usa DOT com>
Date: Thu, 20 Aug 2015 18:21:27 -0400
Message-ID: <CAHV8iDGU8tN+58LR10e3zHxiEsr5ekXrKrLeyYRAD0tx0H6B1A@mail.gmail.com>
Subject: Re: Some programs (vi, ssh) crash when screen buffer height is big
From: Sous Lesquels <a9f54d2 AT gmail DOT com>
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

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 valid 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’ve 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 “-c q” 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 “completely fresh…Cygwin”, do you mean that you didn’t even start with an archive of downloaded packages?

Yep - I basically had a fresh Win 7 and used internet to download all things.

>  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’t know if this is relevant, but have you done a memtest86 (or similar) pass on that machine?  Dodgy RAM could explain intermittent calloc() 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=\[\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