X-Recipient: archive-cygwin AT delorie DOT com 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=sOaf0PIA4t989C5b+dV9TTKrwn3e qdzzd+jaoLadp09RJ4o8Xy1K5G97VHChIuk3osBR+5w2iNn5KF8BVxEbJ/9+8tIs rQlWchFNmBRUf/sH74HzFBpPrOcWD569lx+Fb2vtsnSzpwm02lWB9b3d43QF56x5 To14BTyX3Qgof7Q= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; 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; s=default; bh=c4z6bRZ21iULd9Ld0AkVcNx54Ls=; b=iL BT/jBf2hGOMElRaT0LR61yMVVYoZeb6KG0nZT8w1nrVG2vhwk2vvjp9PirYa6rZQ gl79Rt2JszCbGtXk3OzYY0wr/bsSV+MMDc/bMolt2FQYKREF+f7qsjGkb0dhtsKw 52rZukvvfAigH3AnPllaMh+wSBmckrLNmTll0V+tI= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.6 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=no version=3.3.2 X-HELO: etr-usa.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 In-Reply-To: Date: Thu, 20 Aug 2015 15:45:28 -0600 Message-Id: <26A19798-1F20-4D52-A311-C8312E0D4621@etr-usa.com> References: To: The Cygwin Mailing List X-IsSubscribed: yes Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t7KLjcZR004826 On Aug 20, 2015, at 10:34 AM, Sous Lesquels wrote: > > I don't think this message will thread correctly. Actually, it did here. > However, just had a completely fresh Win7 and Cygwin install You are aware that Microsoft is giving out free Windows 10 upgrades to valid Windows 7 license holders, right? http://www.microsoft.com/en-us/windows/windows-10-upgrade I bring it up not just because it’s the new shiny, but also because I continue to be unable to reproduce your symptom under Windows 10, and Microsoft did a huge amount of work on the Windows console in this release: https://goo.gl/t9KXpC I’ve also failed to reproduce your symptom under MinTTY, though you may be interested to know that the test cycle completes in about 1/12 the time here. :) (Over 2 min for cmd.exe vs about 10 sec for MinTTY.) (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.) I did 5+ test runs under each console. When you say “completely fresh…Cygwin”, do you mean that you didn’t even start with an archive of downloaded packages? Did you use a different package mirror? 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. -- 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