public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: John Hood <cgull@glup.org>
To: cygwin@cygwin.com
Subject: Re: Vim responds too slow on the latest snapshot of cygwin1.dll
Date: Wed, 08 Jun 2016 01:21:00 -0000	[thread overview]
Message-ID: <2345c1b0-1a18-f445-2d45-4c29ac4e9055@glup.org> (raw)
In-Reply-To: <20160606145242.GB4919@calimero.vinschen.de>

It has taken way too long to get a usable Win7 VM set up, but I can
confirm that the 2.5.2.0.1 snapshot works well on Win7 with my test
programs and fixes the issues noted in Corinna's commits, and is
somewhat faster than 2.5.1.  The snapshot's issues with Win7 were also
worse than others have reported, I saw select() locking up and not
responding to either timeout or events.  Definitely something that
should not have reached a release.

I'll apologize for the bugs, they're clearly regressions from what I had
done.  I think I introduced bugs when I reworked the commits to
eliminate changes to cygwait.h, and didn't test sufficiently (I'd
migrated both my Win7 machines to Win10).

regards,

  --jh

On 06/06/2016 10:52, Corinna Vinschen wrote:
> On Jun  6 09:50, Chris Sutcliffe wrote:
>> On 6 June 2016 at 07:05, Takashi Yano wrote:
>>>> Just as John I can't reproduce this.  What OS version do you run this
>>>> on, and is it 32, 32 under WOW64, or 64 bit?
>>> OS: Windows 7 (64bit)
>>> Cygwin: Both 32bit and 64bit
>>>
>>> I have tested on two Win7 machines, and the problem
>>> occurs on both machines.
>>>
>>> Further, this problem occurs in Windows 7, but does
>>> not occur in Windows 10, as far as I tested.
>>>
>>> Can you possibly test on Win7 machine?
>> I can confirm that I see this behaviour on 64bit Windows 7 running
>> 64bit Cygwin using the newly released snapshot (06/06/16).  If there
>> is anything I can do to assist with debugging the issue please let me
>> know.
> Thanks for the offer.  I could actually reproduce it on a W7 32 bit
> machine.  I found the problem and fixed it.  While I was at it, I
> improved the timer handling in select_stuff::wait a bit.
>
> What I'd *really* need now is people testing the latest snapshot on
> https://cygwin.com/snapshots/ ASAP and throw at it what they can think
> of.  Is there still a regression compared to 2.5.1?  If so, please
> report.
>
>
> Thanks to all of you,
> Corinna
>


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

  parent reply	other threads:[~2016-06-08  1:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-05 15:33 Takashi Yano
2016-06-06  8:43 ` Corinna Vinschen
2016-06-06 11:06   ` Takashi Yano
2016-06-06 13:50     ` Chris Sutcliffe
2016-06-06 14:52       ` Corinna Vinschen
2016-06-06 16:15         ` Chris Sutcliffe
2016-06-07 12:38         ` Takashi Yano
2016-06-07 13:12           ` Corinna Vinschen
2016-06-08  1:21         ` John Hood [this message]
2016-06-08  9:00           ` Corinna Vinschen

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=2345c1b0-1a18-f445-2d45-4c29ac4e9055@glup.org \
    --to=cgull@glup.org \
    --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).