Re: Console output hangs in the middle of a line

[Orgad Shaneh <orgads@gmail.com>]

Hi and thanks for replying.

On Wed, 16 Feb 2022 12:01:07 +0200
Takashi Yano wrote:
> On Wed, 16 Feb 2022 18:59:05 +0900
> Takashi Yano wrote:
> > 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?

mkdir -p chunked
cd chunked
git init
mkdir -p abc/def/ghi/jkl def
cd abc/def/ghi/jkl
touch foo
git add foo
seq 1 1000 | xargs touch
cd ../../../../def
seq 1 10000 | xargs touch
cd ..
git clean -dfx

Notice that the long operation of cleaning def (that only writes a
single line) is not printed immediately. The output here looks like
this:
Removing abc/def/ghi/jkl/1
Removing abc/def/ghi/jkl/10
Removing abc/def/ghi/jkl/100
Removing abc/def/ghi/jkl/1000
Removing abc/def/ghi/jkl/101
Removing abc/def/ghi/jkl/102
...
Removing abc/def/ghi/jkl/991
Removing ab<hangs>
c/def/ghi/jkl/992
Removing abc/def/ghi/jkl/993
Removing abc/def/ghi/jkl/994
Removing abc/def/ghi/jkl/995
Removing abc/def/ghi/jkl/996
Removing abc/def/ghi/jkl/997
Removing abc/def/ghi/jkl/998
Removing abc/def/ghi/jkl/999
Removing def/

> And, also please check if this issue occurs in command prompt?
> (I mean not in Windows Terminal, but cmd.exe.)

It does.

Please include me when replying. I'm not registered to the mailing list.

- Orgad