From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: problems with gnus having just updated emacs from git
Date: Tue, 26 Jan 2021 14:04:27 +0000 [thread overview]
Message-ID: <874kj3g5g4.fsf@ucl.ac.uk> (raw)
Hello all,
I have just updated Emacs from git. Since then, gnus is very slow
and/or unresponsive. Specifically, if I open a group,
e.g. gmane.emacs.devel, it seems to be loading *all* the headers which
takes some time (several hundred MB) whereas it did not use to do
this. Further, if I try to enter gmane.emacs.gnus.general in particular
(wanting to post this message), it gets stuck in retrieving or
processing a particular header. Debug on quit gives:
,----
| Debugger entered--Lisp error: (quit)
| nnheader-parse-nov(65073)
| #f(compiled-function () #<bytecode 0x7fcdc25d053635>)()
| gnus-get-newsgroup-headers-xover((1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 ...) nil #<hash-table equal 61664/92170 0x155e9054df5f> "nntp+news.gwene.org:gmane.emacs.gnus.general")
| gnus-agent-retrieve-headers((84607) "nntp+news.gwene.org:gmane.emacs.gnus.general" t)
| gnus-retrieve-headers((84607) "nntp+news.gwene.org:gmane.emacs.gnus.general" t)
| gnus-fetch-headers((84607))
| gnus-cache-retrieve-headers((84607 86510 86518) "nntp+news.gwene.org:gmane.emacs.gnus.general" t)
| gnus-retrieve-headers((84607 86510 86518) "nntp+news.gwene.org:gmane.emacs.gnus.general" t)
| gnus-fetch-headers((84607 86510 86518))
| gnus-select-newsgroup("nntp+news.gwene.org:gmane.emacs.gnus.general" nil nil)
| gnus-summary-read-group-1("nntp+news.gwene.org:gmane.emacs.gnus.general" nil t nil nil nil)
| gnus-summary-read-group("nntp+news.gwene.org:gmane.emacs.gnus.general" nil t nil nil nil nil)
| gnus-group-read-group(nil t)
| gnus-group-select-group(nil)
`----
No matter how long (or short) a time I wait, it's always that header
(84607) that it seems to be stuck on.
In any case, I have had a look at the git log and one commit (from March
2020 but only merged recently I guess as it is listed in between other
commits from the last 10 days) stands out:
,----
| commit 20add1cd22f9775a4475148b300cf2a4de4bd54a
| Author: Eric Abrahamsen <eric@ericabrahamsen.net>
| Date: Tue Mar 17 20:53:05 2020 -0700
|
| Allow gnus-retrieve-headers to return headers directly
`----
Thoughts?
Thank you,
eric
--
Eric S Fraga via Emacs 28.0.50 & org 9.4.4 on Debian bullseye/sid
next reply other threads:[~2021-01-26 14:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 14:04 Eric S Fraga [this message]
2021-01-26 16:46 ` Eric Abrahamsen
2021-01-26 16:50 ` Eric S Fraga
2021-01-26 16:57 ` Eric Abrahamsen
2021-01-27 12:25 ` Eric S Fraga
2021-01-27 12:33 ` Eric S Fraga
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=874kj3g5g4.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=ding@gnus.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.
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).