From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: Gnus from CVS, Emacs from CVS --> out of memory?
Date: Thu, 15 May 2003 10:16:50 -0500 [thread overview]
Message-ID: <uel30utnh.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <84r8705y0l.fsf@lucy.is.informatik.uni-duisburg.de>
kai.grossjohann@gmx.net (Kai Großjohann) writes:
> Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
>
>> Alternatively, have you checked the message log? Do you have any idea
>> how many groups were fetched before the error? If the error always
>> occurs in one group, you might be able to trace the execution in that
>> group prior to out-of-memory.
>
> Ah, now I got an Emacs where I could do something after the OOM. It
> was fetching nnimap+du:INBOX.spamspam. I've now increased the group
> level to > gnus-agent-handle-level. Seems to have done the trick.
>
> Alas, I have no idea what might have been the problem, here. Gnus
> was also complaining about "Invalid line 42" or "Invalid entry 42" or
> "Invalid overview data 42" or something like this, for values of 42
> ranging from 1 to about 8,000.
>
> I wish I had the patience to get to the bottom of this. I still have
> the ~/News/agent/nnimap/du/INBOX/spamspam directory, if that helps?
Take a look at the .overview file for articles 1 through 8,000.
What's wrong with these lines? Would it cause read to consume memory?
Kevin
next prev parent reply other threads:[~2003-05-15 15:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 13:40 Kai Großjohann
2003-05-10 0:44 ` Xavier Maillard
2003-05-10 20:25 ` Kevin Greiner
2003-05-13 12:29 ` Kai Großjohann
2003-05-13 14:10 ` Kevin Greiner
2003-05-13 15:13 ` Kai Großjohann
2003-05-13 19:51 ` Kevin Greiner
2003-05-15 10:01 ` Kai Großjohann
2003-05-15 15:16 ` Kevin Greiner [this message]
2003-05-18 9:27 ` Kai Großjohann
2003-05-13 17:03 ` Dave Love
2003-05-13 23:21 ` Harry Putnam
2003-05-14 0:29 ` Harry Putnam
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=uel30utnh.fsf@xpediantsolutions.com \
--to=kgreiner@xpediantsolutions.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).