From: "Henry S. Thompson" <ht@inf.ed.ac.uk>
To: cygwin@cygwin.com
Subject: gpg-agent stuck at 100%
Date: Tue, 02 Aug 2022 14:43:33 +0100 [thread overview]
Message-ID: <f5ba68m3gmy.fsf@ecclerig.inf.ed.ac.uk> (raw)
>: cygcheck -c cygwin gnupg2
cygwin 3.3.5-1 OK
gnupg2 2.2.35-1 OK
About once a week, gpg-agent starts consuming 100% of a CPU according
to top, and any client that tries to get an answer from it hangs.
kill -9 doesn't succeed. Killing with Process Explorer works, and
then everything is OK for another week or so.
Anyone else experiencing this? Any advice on how to debug?
Thanks,
ht
--
Henry S. Thompson, School of Informatics, University of Edinburgh
10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
URL: http://www.ltg.ed.ac.uk/~ht/
[mail from me _always_ has a .sig like this -- mail without it is forged spam]
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
next reply other threads:[~2022-08-02 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 13:43 Henry S. Thompson [this message]
2022-08-11 19:50 ` Marco Atzeri
2022-08-11 20:53 ` Henry S. Thompson
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=f5ba68m3gmy.fsf@ecclerig.inf.ed.ac.uk \
--to=ht@inf.ed.ac.uk \
--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).