From: Tassilo Horn <tsdh@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: "Adam Sjøgren" <asjo@koldfront.dk>, ding@gnus.org, emacs-devel@gnu.org
Subject: Re: Rendering regression in Gnus with gnus-treat-from-gravatar
Date: Wed, 22 Apr 2020 19:32:39 +0200 [thread overview]
Message-ID: <875zdrs9xk.fsf@gnu.org> (raw)
In-Reply-To: <m24ktbvaa3.fsf@gmail.com> (Robert Pluim's message of "Wed, 22 Apr 2020 16:56:52 +0200")
Robert Pluim <rpluim@gmail.com> writes:
>>>>>> On Wed, 22 Apr 2020 16:39:02 +0200, Tassilo Horn <tsdh@gnu.org> said:
> >> And it happened two or three times that upon clicking a
> >> message, Emacs started consuming 100% CPU and stuck at least 30
> >> seconds before I hit C-g. At one occurrence, I attached GDB
> >> after waiting at least 30 seconds for the full message to
> >> appear and on the bottom of the call stack was
> >>
> >> dns-query
> >> accept-process-output
>
> Tassilo> It just happened again, and this time I made a full C and Lisp
> Tassilo> backtrace (attached).
> Tassilo> I guess I should make a new bug report for that, right?
>
> Yes please.
It's bug#40775.
Bye,
Tassilo
next prev parent reply other threads:[~2020-04-22 17:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <877dym5fes.fsf@tullinup.koldfront.dk>
2020-04-11 14:15 ` Robert Pluim
2020-04-11 15:16 ` Adam Sjøgren
2020-04-11 16:53 ` Robert Pluim
2020-04-14 13:14 ` Robert Pluim
2020-04-14 15:46 ` Eli Zaretskii
2020-04-14 17:32 ` Adam Sjøgren
2020-04-15 8:15 ` Robert Pluim
2020-04-15 9:41 ` Eli Zaretskii
2020-04-15 10:13 ` Robert Pluim
2020-04-15 11:38 ` Eli Zaretskii
2020-04-15 11:55 ` Robert Pluim
2020-04-15 12:01 ` Eli Zaretskii
2020-04-15 13:54 ` Robert Pluim
2020-04-15 14:12 ` Eli Zaretskii
2020-04-15 14:20 ` Robert Pluim
2020-04-22 14:25 ` Tassilo Horn
2020-04-22 14:39 ` Tassilo Horn
2020-04-22 14:56 ` Robert Pluim
2020-04-22 17:32 ` Tassilo Horn [this message]
2020-04-22 14:59 ` Robert Pluim
2020-04-22 17:01 ` Tassilo Horn
2020-04-22 17:23 ` Robert Pluim
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=875zdrs9xk.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=asjo@koldfront.dk \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=rpluim@gmail.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 NNTP newsgroup(s).