From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Cc: Orgad Shaneh <orgads@gmail.com>
Subject: Re: Typed characters are mis-ordered when CPU usage is high
Date: Thu, 3 Mar 2022 09:02:08 +0900 [thread overview]
Message-ID: <20220303090208.4a04e35756b7868fe9b4701d@nifty.ne.jp> (raw)
In-Reply-To: <CAGHpTBLc9waVzjKWb84C5KS+s9uKENrOMAxxfBBrvPR-zKKtPQ@mail.gmail.com>
On Wed, 2 Mar 2022 22:13:30 +0200
Orgad Shaneh wrote:
> On Wed, Mar 2, 2022 at 1:13 AM Takashi Yano <takashi.yano@nifty.ne.jp> wrote:
> >
> > Hi Orgad,
> >
> > On Sun, 27 Feb 2022 23:53:03 +0900
> > Takashi Yano wrote:
> > > On Sun, 27 Feb 2022 16:39:24 +0200
> > > Orgad Shaneh wrote:
> > > > Hi,
> > > >
> > > > I'm using cygwin runtime 3.3.4-2.
> > > >
> > > > When a foreground job is running, and the general CPU usage of the
> > > > machine is high, characters are mis-ordered.
> > > >
> > > > To reproduce, I use this script to produce load:
> > > > #!/bin/sh
> > > >
> > > > for i in $(seq $(nproc)); do
> > > > while true; do :; done &
> > > > done
> > > > wait
> > > >
> > > > Run it in the background, then run a long foreground job, and while it
> > > > is running, type something.
> > > >
> > > > Example:
> > > > $ spin.sh &
> > > > $ sleep 3 # While it is running, I quickly typed git status
> > > > $ sigt tatus
> > > >
> > > > This reproduces on Windows Terminal and on cmd (Cygwin.bat)
> > >
> > > Thanks for the report.
> > >
> > > I think this is due to a bug which I recently fixed.
> > > https://cygwin.com/pipermail/cygwin-patches/2022q1/011791.html
> >
> > Now, new developer snapshot is ready: https://cygwin.com/snapshots/
> > Please try.
>
> Tested. Looks much better. Thanks!
Thanks for testing. But what do you mean by 'better'?
Do you mean that the problem still happens in lower probability?
> Is a release planned soon?
This fix was also applied in cygwin-3_3-branch, so the next
release (probabliy 3.3.5) will come with the fix.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2022-03-03 0:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-27 14:39 Orgad Shaneh
2022-02-27 14:53 ` Takashi Yano
2022-03-01 23:12 ` Takashi Yano
2022-03-02 20:13 ` Orgad Shaneh
2022-03-03 0:02 ` Takashi Yano [this message]
2022-03-03 3:46 ` Orgad Shaneh
2022-03-10 13:17 ` Orgad Shaneh
2022-03-11 21:36 ` Takashi Yano
2022-03-17 18:40 ` Orgad Shaneh
2022-03-18 4:23 ` Takashi Yano
2022-03-18 5:22 ` Takashi Yano
2022-03-18 5:57 ` Orgad Shaneh
2022-03-18 6:30 ` Takashi Yano
2022-03-18 6:32 ` Orgad Shaneh
2022-03-18 11:21 ` Orgad Shaneh
2022-03-18 12:15 ` Takashi Yano
2022-03-18 13:04 ` Orgad Shaneh
2022-03-18 13:28 ` Takashi Yano
2022-03-18 6:11 ` n952162
2022-03-02 20:28 ` Kaz Kylheku (Cygwin)
2022-03-03 0:29 ` Takashi Yano
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=20220303090208.4a04e35756b7868fe9b4701d@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin@cygwin.com \
--cc=orgads@gmail.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).