From: Derek Pagel <Derek.Pagel@infor.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Slow cygwin command waiting for cygcons.input.mutex.0
Date: Thu, 20 Jul 2023 20:58:28 +0000 [thread overview]
Message-ID: <CH2PR02MB6024C14B159D903A1E00F93BE53EA@CH2PR02MB6024.namprd02.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 736 bytes --]
I have been able to replicate Cygwin commands hanging on a Windows 2019 server by running a program that loops through cp, mv, chmod and rm 100 times every 15 mins. I'm also running each of those Cygwin commands through a Microsoft utility that reports which specific Windows API a thread has called when it's stuck. Eventually, I captured this output on the chmod command from that tool:
Process 0x1c34 - chmod.exe
----------------------------------
8080: [1c34:1f90:b]->[Mutex:\BaseNamedObjects\cygwin1S5-144f71ebfd861cae\cygcons.input.mutex.0]->[1c34:160c:r]->[End]
7384: [1c34:1cd8:b]->[End]
5644: [1c34:160c:r]->[End]
It looks like it's waiting for some sort of input from somewhere. Has anyone seen anything like this?
reply other threads:[~2023-07-20 20:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CH2PR02MB6024C14B159D903A1E00F93BE53EA@CH2PR02MB6024.namprd02.prod.outlook.com \
--to=derek.pagel@infor.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).