From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: info-gnus-english@gnu.org
Subject: Re: persistent articles weirdness
Date: Fri, 03 Sep 2010 21:20:37 +0200 [thread overview]
Message-ID: <m3sk1qbpmi.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <94979c3f-56be-4411-8ffe-859104b6ae0d@x25g2000yqj.googlegroups.com>
Francis Moreau <francis.moro@gmail.com> writes:
> First sometimes (actually this happens quite often) something in gnus
> internal get corrupted and gnus get stuck trying to display the
> summary buffer. The cpu usage is at 100%.
Try `(setq debug-on-quit t)' and then `C-g' when it gets stuck. That'll
give you a backtrace that you can post here.
> Funny enough, the authors of gnus know that this (bug) exists and
We do?
> offered some commands to fix it:
>
> - M-x gnus-cache-generate-nov-databases
> - M-x gnus-cache-generate-active
Anything can become corrupted.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
parent reply other threads:[~2010-09-03 19:20 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <94979c3f-56be-4411-8ffe-859104b6ae0d@x25g2000yqj.googlegroups.com>]
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=m3sk1qbpmi.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=info-gnus-english@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.
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).