This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Some programs (vi, ssh) crash when screen buffer height is big

Greetings, Warren Young!

> 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?

And you did read the Win10 EULA, right?


> 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:


That doesn't help people who don't want to install spying OS on their
And that's just one of the reasons people don't want to deal with it.

> 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.

With best regards,
Andrey Repin
Friday, August 21, 2015 01:29:23

Sorry for my terrible english...

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]