public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Aaron Digulla" <digulla@hepe.com>
To: cygwin@cygwin.com
Subject: Re: Windows locks up when pressing Ctrl+S while native process writes to terminal
Date: Thu, 03 Dec 2015 13:57:00 -0000	[thread overview]
Message-ID: <3fb3-56604a80-79-5a531800@63692284> (raw)
In-Reply-To: <1cb3-56530100-91-40254200@154582263>


This seems to be a consistent bug. How do I file it?

> Am Sonntag, 22. November 2015 20:17 CET, Thomas Wolff <towo@towo.net> schrieb:
>
> > > I found a consistent bug that happens every time:
> > > ...
> > > - Press Ctrl+S to stop the output in the terminal
> > >
> > > Bug #1: It's not possible to unfreeze the output in the terminal with Ctrl+Q. It just stays "stuck"
> > I confirm this effect and you don't need a fat application to
> > demonstrate it. With this Windows cmd script loop.bat:
> > @echo off
> > set n=0
> > :loop
> > echo %n%
> > echo %n% >> .log
> > set /A n=%n% + 1
> > ping 127.0.0.1 -n 2 > nul
> > goto loop
> >
> > run it: ./loop.bat, then use ^S; the script will actually continue to
> > run but will not show any more output in a pty-based terminal (works in
> > Cygwin console).
>
> Okay. So it seems to be a consistent bug which only affects me. What happens next?
>
> > > Bug #2: After a few seconds, the disk starts to trash. ...
> > Thrashing? Might be caused by the apparently-stopped application going
> > into some endless-loop activity.
>
> I feel that Windows runs out of memory but I have no idea why. If cygwin uses the standard OS services to create pipes between processes, there will be a 4KB buffer which the native process can fill and that's it. It should then block in a call to `write()` (or the equivalent) and not be able to do anything.
>
> I have about 2-3GB free RAM, so even if pipe would buffer all the output, it shouldn't be able to make Windows run out of memory. The Maven build reads and write files but all in all, we're talking 40-60MB tops.
>
> I'm a bit reluctant to run more tests since it takes my computer so long to heal (it's actually my company's  computer, so I'm supposed to work, not wait for it to heal after testing a cygwin bug :-).
>
> Regards,
>
> --
> Aaron "Optimizer" Digulla a.k.a. Philmann Dark
> "It's not the universe that's limited, it's our imagination.
> Follow me and I'll show you something beyond the limits."
> http://blog.pdark.de/
>
>
> --
> 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
>
>



--
Aaron "Optimizer" Digulla a.k.a. Philmann Dark
"It's not the universe that's limited, it's our imagination.
Follow me and I'll show you something beyond the limits."
http://blog.pdark.de/


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

      reply	other threads:[~2015-12-03 13:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-13 10:08 Aaron Digulla
2015-11-20 13:49 ` Aaron Digulla
2015-11-22 19:18 ` Thomas Wolff
2015-11-23 12:04   ` Aaron Digulla
2015-12-03 13:57     ` Aaron Digulla [this message]

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=3fb3-56604a80-79-5a531800@63692284 \
    --to=digulla@hepe.com \
    --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).