From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 69561@debbugs.gnu.org
Subject: bug#69561: 30.0.50; Freeze from M-x gnus on macOS
Date: Tue, 05 Mar 2024 18:54:43 +0100 [thread overview]
Message-ID: <m2wmqgftss.fsf@Pro.fritz.box> (raw)
In-Reply-To: <86jzmglixy.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 05 Mar 2024 18:52:41 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Gerd Möllmann <gerd.moellmann@gmail.com>
>> Cc: 69561@debbugs.gnu.org
>> Date: Tue, 05 Mar 2024 17:38:14 +0100
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > But wait: epg-wait-for-status seems to wait for one or more processes
>> > to exit. So what is the status of the process for which it waits? Is
>> > it running, or did it perhaps already exit?
>>
>> I could see gpg running in Activity Monitor.
>
> "Running" as in "consuming CPU", or just didn't exit yet?
Sorry, I don't know. I just saw gpg in the list.
> Maybe you should attach a debugger to gpg and try to understand what
> is it doing and why it doesn't exit?
>
>> I'm currently trying to bisect when this problem started. I can't force
>> the freeze to happen, but I hope that surviving a day or two can be
>> counted as a good version, when it freezes at leasst once a day with
>> master. Maybe I can find the culprit that way.
>
> Could be. But if you could establish why gpg isn't exiting, you could
> perhaps make progress faster.
Maybe, but the bisecting has at least the davantage that I can do what I
really wanted to, and just wait for Emacs to eventually freeze or not.
And the builds in between can also run unattended. TRT for a lazy old
lad ;-).
next prev parent reply other threads:[~2024-03-05 17:54 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 10:59 bug#69561: 30.0.50; Freeze from M-x gnus on macOS Gerd Möllmann
2024-03-05 11:04 ` Gerd Möllmann
2024-03-05 14:29 ` Gerd Möllmann
2024-03-05 15:46 ` Eli Zaretskii
2024-03-05 16:38 ` Gerd Möllmann
2024-03-05 16:52 ` Eli Zaretskii
2024-03-05 17:54 ` Gerd Möllmann [this message]
2024-03-07 15:18 ` Gerd Möllmann
2024-03-07 15:52 ` Gerd Möllmann
2024-03-07 16:05 ` Alan Third
2024-03-07 16:30 ` Gerd Möllmann
2024-03-07 16:49 ` Alan Third
2024-03-07 17:01 ` Gerd Möllmann
2024-03-07 18:47 ` Alan Third
2024-03-07 19:29 ` Gerd Möllmann
2024-03-07 20:23 ` Gerd Möllmann
2024-03-08 4:31 ` Gerd Möllmann
2024-03-09 7:33 ` Eli Zaretskii
2024-03-09 9:47 ` Gerd Möllmann
2024-03-09 10:07 ` Eli Zaretskii
2024-03-09 11:00 ` Gerd Möllmann
2024-03-09 11:11 ` Eli Zaretskii
2024-03-09 11:33 ` Gerd Möllmann
2024-03-09 13:08 ` Eli Zaretskii
2024-03-09 13:21 ` Gerd Möllmann
2024-03-09 13:27 ` Eli Zaretskii
2024-03-09 13:51 ` Gerd Möllmann
2024-03-13 6:11 ` Gerd Möllmann
2024-03-13 16:53 ` Filipp Gunbin
2024-03-13 18:18 ` Gerd Möllmann
2024-03-13 18:20 ` Gerd Möllmann
2024-03-13 19:20 ` Filipp Gunbin
2024-03-13 19:37 ` Gerd Möllmann
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=m2wmqgftss.fsf@Pro.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=69561@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.