public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Cc: Anon User <retry0001-vps@yahoo.com>
Subject: Re: Mintty/tmux hangs for 1 minute on startup - seems to be a forking issue
Date: Sun, 02 Feb 2020 08:59:00 -0000	[thread overview]
Message-ID: <20200202175906.5b8555b900204b8adc65637b@nifty.ne.jp> (raw)
In-Reply-To: <1041498587.530757.1580632311715@mail.yahoo.com>

On Sun, 2 Feb 2020 08:31:51 +0000 (UTC)
"Anon User via cygwin" wrote:
> Same behavior as mintty, tmux, the previous test case, with TaskManager's analyze wait chain saying it's waiting on Network I/O.
> 
>  $ ./a.exeStarted.
> ** 1 min wait here **
> CreatePseudoConsole() end.ClosePseudoConsole() end.

From this result, it seems that this is not a cygwin problem.
But your system has a problem regarding CreatePseudoConsole() call.

I guess Microsoft's OpenSSH server also behaves the same.

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

--
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:[~2020-02-02  8:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <595178088.221931.1580542748412.ref@mail.yahoo.com>
2020-02-01  7:39 ` Anon User via cygwin
2020-02-01 15:13   ` Takashi Yano
2020-02-01 17:41   ` Anon User via cygwin
2020-02-01 23:11     ` Takashi Yano
2020-02-01 23:25       ` Anon User via cygwin
2020-02-02  7:01         ` Takashi Yano
2020-02-02  8:31           ` Anon User via cygwin
2020-02-02  8:59             ` Takashi Yano [this message]
2020-02-02  9:14               ` Anon User via cygwin
2020-02-02  9:27                 ` Takashi Yano
2020-02-02  9:33                   ` Anon User via cygwin
2020-02-02  9:48                   ` Anon User via cygwin
2020-02-02 18:10                     ` Bengt-Arne Fjellner via cygwin

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=20200202175906.5b8555b900204b8adc65637b@nifty.ne.jp \
    --to=takashi.yano@nifty.ne.jp \
    --cc=cygwin@cygwin.com \
    --cc=retry0001-vps@yahoo.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).