From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: Console output hangs in the middle of a line
Date: Wed, 16 Feb 2022 18:59:05 +0900 [thread overview]
Message-ID: <20220216185905.06b32cba3523fb612bf4d042@nifty.ne.jp> (raw)
In-Reply-To: <CAGHpTBJ1JHS5=3WBNjkRP3f8i2gqQPRU7Kv6jj9gTj1Nc3BrcQ@mail.gmail.com>
On Wed, 16 Feb 2022 11:49:36 +0200
Orgad Shaneh wrote:
> I'm using cygwin runtime 3.3.4-2. CYGWIN env variable is empty.
> Running in Windows Terminal.
>
> When I run git clean -dfx on a Node.JS project, which has huge
> node_modules directories, that produces a lot of output in high rate,
> the console seems to freeze for very long in the middle of a line, and
> continues after a while. If I get it correctly, the writes are done in
> 4K chunks, freezing for a few seconds after each chunk.
>
> The output looks more or less like this:
>
> Removing common/auth.js
> Removing common/auth.js.map
> ...
> Removing common/bar.js
> Removing common/bar.js.map
> Remo<freeze for about 20s after 4K bytes>
> ving common/foo.js (continued on the same line)
> Removing common/foo.js.map
> ...
> etc.
>
> No output was lost.
>
> Is this a known issue?
Could you please provide reproducible steps for the issue?
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2022-02-16 9:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-16 9:49 Orgad Shaneh
2022-02-16 9:59 ` Takashi Yano [this message]
2022-02-16 10:01 ` Takashi Yano
2022-02-20 11:43 ` Orgad Shaneh
2022-02-20 13:37 ` Takashi Yano
2022-02-20 13:43 ` Takashi Yano
2022-02-20 13:48 ` Takashi Yano
2022-02-20 13:51 ` Orgad Shaneh
2022-02-20 14:22 ` Takashi Yano
2022-02-20 14:34 ` Takashi Yano
2022-02-20 14:42 ` Orgad Shaneh
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=20220216185905.06b32cba3523fb612bf4d042@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--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).