Gnus development mailing list
 help / color / mirror / Atom feed
* problems with gnus having just updated emacs from git
@ 2021-01-26 14:04 Eric S Fraga
  2021-01-26 16:46 ` Eric Abrahamsen
  0 siblings, 1 reply; 6+ messages in thread
From: Eric S Fraga @ 2021-01-26 14:04 UTC (permalink / raw)
  To: ding

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



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: problems with gnus having just updated emacs from git
  2021-01-26 14:04 problems with gnus having just updated emacs from git Eric S Fraga
@ 2021-01-26 16:46 ` Eric Abrahamsen
  2021-01-26 16:50   ` Eric S Fraga
  0 siblings, 1 reply; 6+ messages in thread
From: Eric Abrahamsen @ 2021-01-26 16:46 UTC (permalink / raw)
  To: Eric S Fraga; +Cc: ding

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> 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
> `----

Yup, that's probably it. It's caused some other difficulties, so I'm
going to back that out of master in a little bit. The above is helpful
for debugging, though! Thanks for reporting.

Eric


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: problems with gnus having just updated emacs from git
  2021-01-26 16:46 ` Eric Abrahamsen
@ 2021-01-26 16:50   ` Eric S Fraga
  2021-01-26 16:57     ` Eric Abrahamsen
  0 siblings, 1 reply; 6+ messages in thread
From: Eric S Fraga @ 2021-01-26 16:50 UTC (permalink / raw)
  To: Eric Abrahamsen; +Cc: ding

On Tuesday, 26 Jan 2021 at 08:46, Eric Abrahamsen wrote:
> Yup, that's probably it. It's caused some other difficulties, so I'm
> going to back that out of master in a little bit. The above is helpful
> for debugging, though! Thanks for reporting.

You're very welcome.  Eventually, gnus did allow me into the gnus group
I mentioned in previous post.  But still very slow, loading all headers
from the server and, funnily enough, displaying all the messages in the
group even though all but one previously seen & read.

Let me know when you've backed it out so I can update & build my emacs
again.

thank you,
eric

-- 
Eric S Fraga via Emacs 28.0.50 & org 9.4.4 on Debian bullseye/sid


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: problems with gnus having just updated emacs from git
  2021-01-26 16:50   ` Eric S Fraga
@ 2021-01-26 16:57     ` Eric Abrahamsen
  2021-01-27 12:25       ` Eric S Fraga
  0 siblings, 1 reply; 6+ messages in thread
From: Eric Abrahamsen @ 2021-01-26 16:57 UTC (permalink / raw)
  To: ding


On 01/26/21 16:50 PM, Eric S Fraga wrote:
> On Tuesday, 26 Jan 2021 at 08:46, Eric Abrahamsen wrote:
>> Yup, that's probably it. It's caused some other difficulties, so I'm
>> going to back that out of master in a little bit. The above is helpful
>> for debugging, though! Thanks for reporting.
>
> You're very welcome.  Eventually, gnus did allow me into the gnus group
> I mentioned in previous post.  But still very slow, loading all headers
> from the server and, funnily enough, displaying all the messages in the
> group even though all but one previously seen & read.

Yes, there's just something wrong with the logic of sorting out which
articles to display, which are cached, and which need to be fetched.

> Let me know when you've backed it out so I can update & build my emacs
> again.

It's out!


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: problems with gnus having just updated emacs from git
  2021-01-26 16:57     ` Eric Abrahamsen
@ 2021-01-27 12:25       ` Eric S Fraga
  2021-01-27 12:33         ` Eric S Fraga
  0 siblings, 1 reply; 6+ messages in thread
From: Eric S Fraga @ 2021-01-27 12:25 UTC (permalink / raw)
  To: ding

On Tuesday, 26 Jan 2021 at 08:57, Eric Abrahamsen wrote:
> It's out!

Thank you.  Building emacs now!

-- 
Eric S Fraga via Emacs 28.0.50 & org 9.4.4 on Debian bullseye/sid



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: problems with gnus having just updated emacs from git
  2021-01-27 12:25       ` Eric S Fraga
@ 2021-01-27 12:33         ` Eric S Fraga
  0 siblings, 0 replies; 6+ messages in thread
From: Eric S Fraga @ 2021-01-27 12:33 UTC (permalink / raw)
  To: ding

... and it's working "properly" again.  Thank you.  But I do look
forward to your improvements with header handling in due course.

-- 
Eric S Fraga via Emacs 28.0.50 & org 9.4.4 on Debian bullseye/sid



^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2021-01-27 12:34 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-01-26 14:04 problems with gnus having just updated emacs from git Eric S Fraga
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

Gnus development mailing list

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.vuxu.org/ding

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 ding ding/ http://inbox.vuxu.org/ding \
		ding@inbox.vuxu.org
	public-inbox-index ding

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.archive.emacs.gnus.general


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git