DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:content-transfer-encoding:message-id
	:references:to; q=dns; s=default; b=IQXfI6nix9wZpglLuuJp9J0SazYn
	o6qcaqkv55C8eYuyNYIjjnzc4u1rJZEtMthoMOM5dLMQTt7dlLR57fs/t6kbctS9
	9T5QlSJPX8zLSvA4D9w46rWE2bINFpcKx3uiD60CNQerMbgN55IUhh5QuIrVF+Ul
	2t4lcQoS91TnOc4=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
Subject: Re: Some programs (vi, ssh) crash when screen buffer height is big
From: Warren Young <wyml@etr-usa.com>
In-Reply-To: <CAHV8iDGU8tN+58LR10e3zHxiEsr5ekXrKrLeyYRAD0tx0H6B1A@mail.gmail.com>
Date: Thu, 20 Aug 2015 16:36:56 -0600
Message-Id: <6DC9320F-4DCC-47E4-AB8C-3158EBD6260E@etr-usa.com>
References: <CAHV8iDH4pG0FoGrckc36atQUV+SWOnryJ-zBDK92HTGgPRC=Ew@mail.gmail.com> <26A19798-1F20-4D52-A311-C8312E0D4621@etr-usa.com> <CAHV8iDGU8tN+58LR10e3zHxiEsr5ekXrKrLeyYRAD0tx0H6B1A@mail.gmail.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Content-Transfer-Encoding: 8bit

On Aug 20, 2015, at 4:21 PM, Sous Lesquels <a9f54d2@gmail.com> wrote:
>> 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

Oh, I’ve been assuming that it was the *length* that matters.  I’m an old-skool kinda guy, so I’ve been keeping it to 80 columns.

After sending the window full-screen, lookee lookee:

2014/11/04 17:40:58 Ending cygwin install
    112 [main] vi 4424 C:\cygwin64\bin\vi.exe: *** fatal error - cmalloc would have returned NULL
/x: line 6:  4424 Hangup                  vi -c q /var/log/setup.log

It happened on the first run, with a 317x85 window and 9999 lines of scrollback buffer.

>> Did you use a different package mirror?
> 
> Yes - I can try with the same mirror if you think that would make a
> difference.

Actually, you did the test I wanted: you proved that a different mirror gives the same results, which rules out bad packages on one rogue mirror.  The chance of two bad mirrors is exceedingly tiny, so we can assume the packages are fine, unless they’re corrupt on sourceware, which is also unlikely.

>> I’ve also failed to reproduce your symptom under MinTTY
> 
> I cannot reproduce under mintty either.

So why not run under mintty, then?  Cygwin runs better under mintty in general.
--
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