Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: Gnus from CVS, Emacs from CVS --> out of memory?
Date: Tue, 13 May 2003 09:10:22 -0500	[thread overview]
Message-ID: <uel33hr8x.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <8465of114j.fsf@lucy.is.informatik.uni-duisburg.de>

kai.grossjohann@gmx.net (Kai Großjohann) writes:

> Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
>
>> The constant dings is the result of running out of memory while trying
>> to generate the "out of memory" alert.  I used to get it when I evaled
>> a form on way too many buffers.
>
> Hehe.
>
>> You might check the size of your group's .overview file.  I managed to
>> get one up to 108M by not running gnus-agent-expire for several
>> months.
>>
>> That seems to be the most likely culpret.  The group's article lists
>> may also be growing but it's hard to believe that they'd be that
>> large.
>
> Hm.  The sum of all .overview files is 111M, distributed over 300 of
> them.  No file is larger than 10M.
>
> (I just deleted some files of 20M each.  But I still get the same
> symtoms.)

What does list-buffers show after you kill the fetch session?  As an
example, I just opened two groups and my .newsrc-dribble file is
already over 3M.

> The article lists, is that the .agentview files?  They are all <100k.

Actually I was thinking of the seen, read, ticked lists in newsrc.eld

Kevin



  reply	other threads:[~2003-05-13 14:10 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 [this message]
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
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=uel33hr8x.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).