public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Paul Kitchen" <pkitchen@talk21.com>
To: <cygwin@cygwin.com>
Subject: Issue with delayed process start and effect on Windows 10
Date: Thu, 02 Feb 2017 15:17:00 -0000	[thread overview]
Message-ID: <000e01d27d67$799691a0$6cc3b4e0$@talk21.com> (raw)

Hi All,

I am a newbie to Cygwin having downloaded it yesterday.

I managed to install it after some time (for the reasons explained below)
and brought up a Cygwin terminal.

During a script run initiated in the Cygwin terminal, I noticed that after a
very short while, the execution would slow down to a crawl.  The script was
running but in very slow motion.

I looked at the sequence of events using a windows sysinternals tool and
found that there is a delay in starting (forking?) a new command (e.g. ls)
of precisely 20 seconds which is strange.  The script runs normally but very
very slowly.

I noticed a side effect too.  After the slowing down in Cygwin, certain
windows apps behaved the same way as though there was cross contamination
from Cygwin.  Windows Task Manager takes about 40 second to appear and same
for the Windows Command Window.  Flash extension in the Chrome browser would
continuously fail to start.  To repair the situation I had to reboot.  To
make sure that Cygwin was not still active, I aborted all bash.exe processes
that were running and the problem continued to persist.

Is this a known problem?  For me it makes Cygwin completely unusable which
is a pity.

Paul Kitchen



--
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:[~2017-02-02 15:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-02 15:17 Paul Kitchen [this message]
2017-02-02 15:35 ` Andrey Repin
2017-02-02 16:51   ` Marco Atzeri
2017-02-02 20:40     ` Paul Kitchen
2017-02-03 22:13     ` Brian Inglis
2017-02-12 11:32       ` Corinna Vinschen
2017-02-02 20:04 ` bzs
2017-02-02 21:12   ` Paul Kitchen
2017-02-02 23:27     ` Eliot Moss
2017-02-03 22:46     ` Brian Inglis

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='000e01d27d67$799691a0$6cc3b4e0$@talk21.com' \
    --to=pkitchen@talk21.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).