From: Vincent Bernat <bernat@luffy.cx>
To: ding@gnus.org
Subject: Re: How to debug hangs during message fetching
Date: Sat, 19 Feb 2011 10:45:49 +0100 [thread overview]
Message-ID: <m3r5b4xsqa.fsf@neo.luffy.cx> (raw)
In-Reply-To: <87vd0jpr27.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 16 Feb 2011 14:12:16 -0800")
Hi!
I have similar problem when using `gnus-group-get-new-news'. However, It
does not happen each time. If I ask for new news by hand, it never
happens. It seems to happen only when the refresh is initiated by gnus
demon. I have something like this:
(defun vince-gnus-demon-scan-mail-and-update ()
(vince-gnus-demon-scan-mail-or-news-and-update 2))
(gnus-demon-add-handler 'vince-gnus-demon-scan-mail-and-update 20 1)
(defun vince-gnus-demon-scan-news-and-update ()
(vince-gnus-demon-scan-mail-or-news-and-update 3))
(gnus-demon-add-handler 'vince-gnus-demon-scan-news-and-update 30 20)
Running by hand those two functions does not trigger the
bug. gnus-demon-handlers list only contain those two functions.
If I refresh the I have only one nnimap backend so it is easy to see
which one hangs. The hang happens with "nnimap read 30k" in the
minibuffer. This is always the same "30k". The nnimap buffer ends with
something like that:
14679 OK [READ-ONLY] Select completed.
* OK [CLOSED] Previous mailbox closed.
* FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
* OK [PERMANENTFLAGS ()] Read-only mailbox.
* 77 EXISTS
* 0 RECENT
* OK [UIDVALIDITY 1176456138] UIDs valid
* OK [UIDNEXT 78] Predicted next UID
* OK [HIGHESTMODSEQ 1] Highest
14680 OK [READ-ONLY] Select completed.
* OK [CLOSED] Previous mailbox closed.
* FLAGS (\Answered \Flagged \Deleted \Seen \Draft gnus-forward)
* OK [PERMANENTFLAGS ()] Read-only mailbox.
* 13108 EXISTS
* 0 RECENT
* OK [UIDVALIDITY 1169990978] UIDs valid
* OK [UIDNEXT 13463] Predicted next UID
* OK [HIGHESTMODSEQ 1] Highest
14681 OK [READ-ONLY] Select completed.
* OK [CLOSED] Previous mailbox closed.
* FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
* OK [PERMANENTFLAGS ()] Read-only mailbox.
* 7059 EXISTS
* 0 RECENT
* OK [UIDVALIDITY 1297203672] UIDs valid
* OK [UIDNEXT 7060] Predicted next UID
* OK [HIGHESTMODSEQ 7061] Highest
14682 OK [READ-ONLY] Select completed.
14683 OK NOOP completed.
14685 OK NOOP completed.
14687 OK NOOP completed.
14689 OK NOOP completed.
Process *nnimap* processus arr.t.
I am currently using 9adfe4a952f2b51c1080ab941930ef5e831cf1d9 but it
happened with more recent checkouts (I did downgrade because of Gcc and
auth-sources problem). It happens with this commit too (for example):
37efc98493b86d09a0a2d198030884ebedeafc75.
The IMAP server is dovecot.
--
BOFH excuse #195:
We only support a 28000 bps connection.
next prev parent reply other threads:[~2011-02-19 9:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 11:31 Tassilo Horn
2011-02-07 11:44 ` Lars Ingebrigtsen
2011-02-07 11:55 ` Tassilo Horn
2011-02-07 11:59 ` Lars Ingebrigtsen
2011-02-07 12:17 ` Tassilo Horn
2011-02-07 12:21 ` Lars Ingebrigtsen
2011-02-07 12:39 ` Tassilo Horn
2011-02-07 12:57 ` Tassilo Horn
2011-02-14 3:35 ` Lars Ingebrigtsen
2011-02-14 9:21 ` Tassilo Horn
2011-02-15 21:28 ` Emilio Jesús Gallego Arias
2011-02-16 22:12 ` Lars Ingebrigtsen
2011-02-16 22:18 ` Emilio Jesús Gallego Arias
2011-02-16 22:24 ` Lars Ingebrigtsen
2011-02-17 0:27 ` Emilio Jesús Gallego Arias
2011-02-17 23:48 ` Lars Ingebrigtsen
2011-02-23 2:12 ` Emilio Jesús Gallego Arias
2011-02-23 2:18 ` Emilio Jesús Gallego Arias
2011-02-23 9:04 ` Lars Ingebrigtsen
2011-02-24 2:18 ` Emilio Jesús Gallego Arias
2011-02-25 3:33 ` Lars Ingebrigtsen
2011-02-19 9:45 ` Vincent Bernat [this message]
2011-02-20 1:22 ` Lars Ingebrigtsen
2011-02-20 13:14 ` Vincent Bernat
2011-02-07 21:21 ` Ludovic Courtès
2011-02-07 21:27 ` Michael Welsh Duggan
2011-02-14 3:35 ` Lars Ingebrigtsen
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=m3r5b4xsqa.fsf@neo.luffy.cx \
--to=bernat@luffy.cx \
--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).