public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Derek Pagel <Derek.Pagel@infor.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Cc: Takashi Yano <takashi.yano@nifty.ne.jp>
Subject: RE: Cygwin commands are intermittently hanging on Windows
Date: Wed, 16 Nov 2022 17:19:22 +0000	[thread overview]
Message-ID: <CH2PR02MB6024CA490473907E10E4A678E5079@CH2PR02MB6024.namprd02.prod.outlook.com> (raw)
In-Reply-To: <20221109022425.ee524a4bde2c0b17259dc987@nifty.ne.jp>

[-- Attachment #1: Type: text/plain, Size: 446 bytes --]

Windows 10 Professional (64 bit) 22H2 Version 10.0.19045.2130
Cygwin: CYGWIN_NT-10.0-19045 HP-Z230 3.3.6-341.x86_64 2022-09-05 11:15 UTC x86_64 Cygwin

And you?

*************************************

We've recreated the hanging issue on Windows 2019 and were able to capture and attach a DMP file of a 'cp' command that was hanging. One other thing that we noticed is that the Cygwin commands each tend to hang about 42 or 43 seconds.


[-- Attachment #2: cp.DMP --]
[-- Type: application/octet-stream, Size: 20206092 bytes --]

  parent reply	other threads:[~2022-11-16 17:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07 22:06 Derek Pagel
2022-11-08  0:24 ` Takashi Yano
2022-11-08 13:25   ` Derek Pagel
2022-11-08 15:41     ` Takashi Yano
2022-11-08 16:00       ` Derek Pagel
2022-11-08 16:50         ` Takashi Yano
2022-11-08 17:17           ` Derek Pagel
2022-11-08 17:24             ` Takashi Yano
2022-11-08 18:11               ` Derek Pagel
2022-11-22 13:23                 ` Derek Pagel
2022-11-16 17:19               ` Derek Pagel [this message]
2022-11-25 21:54                 ` 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=CH2PR02MB6024CA490473907E10E4A678E5079@CH2PR02MB6024.namprd02.prod.outlook.com \
    --to=derek.pagel@infor.com \
    --cc=cygwin@cygwin.com \
    --cc=takashi.yano@nifty.ne.jp \
    /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).