From: Warren Young <wyml@etr-usa.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Some programs (vi, ssh) crash when screen buffer height is big
Date: Thu, 20 Aug 2015 21:45:00 -0000 [thread overview]
Message-ID: <26A19798-1F20-4D52-A311-C8312E0D4621@etr-usa.com> (raw)
In-Reply-To: <CAHV8iDH4pG0FoGrckc36atQUV+SWOnryJ-zBDK92HTGgPRC=Ew@mail.gmail.com>
On Aug 20, 2015, at 10:34 AM, Sous Lesquels <a9f54d2@gmail.com> 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
next prev parent reply other threads:[~2015-08-20 21:45 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 16:35 Sous Lesquels
2015-08-20 21:45 ` Warren Young [this message]
2015-08-20 22:21 ` Sous Lesquels
2015-08-20 22:36 ` Warren Young
2015-08-21 12:37 ` Sous Lesquels
2015-08-21 18:53 ` Warren Young
2015-08-21 21:41 ` Thomas Wolff
2015-08-24 12:08 ` Philip Daniels
2015-08-25 16:35 ` Sous Lesquels
2015-08-25 16:47 ` cyg Simple
2015-08-27 19:47 ` Sous Lesquels
2015-08-28 13:23 ` Larry Hall (Cygwin)
2015-08-28 14:05 ` Sous Lesquels
2015-08-28 18:50 ` Larry Hall (Cygwin)
2015-08-28 21:31 ` Sous Lesquels
2015-08-28 21:53 ` Warren Young
2015-08-28 23:24 ` Warren Young
2015-08-25 18:20 ` Andrey Repin
2015-08-27 20:00 ` Sous Lesquels
2015-08-28 14:48 ` Andrey Repin
2015-08-28 21:09 ` Sous Lesquels
2015-08-28 23:27 ` Andrey Repin
2015-08-20 22:35 ` Andrey Repin
-- strict thread matches above, loose matches on Subject: below --
2014-07-16 20:10 sous lesquels
2014-07-16 20:30 ` sous lesquels
2014-07-17 2:13 ` Christopher Faylor
2014-07-17 8:24 ` Corinna Vinschen
2014-07-18 3:28 ` Warren Young
2014-07-18 14:48 ` sous lesquels
2014-07-18 15:51 ` Larry Hall (Cygwin)
2014-07-18 16:59 ` sous lesquels
2014-07-18 17:59 ` Christopher Faylor
2014-07-18 18:48 ` Nellis, Kenneth
2014-07-18 20:35 ` sous lesquels
2014-07-21 12:32 ` Nellis, Kenneth
2014-07-23 0:50 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=26A19798-1F20-4D52-A311-C8312E0D4621@etr-usa.com \
--to=wyml@etr-usa.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).