Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Memory exhausted while saving .newsrc.eld
Date: Sun, 30 Mar 2003 04:23:51 +0200	[thread overview]
Message-ID: <m37kah7ft4.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <uk7fp8g6i.fsf@xpediantsolutions.com> (Kevin Greiner's message of "Mon, 24 Feb 2003 16:30:45 -0600")

Kevin Greiner <kgreiner@xpediantsolutions.com> writes:

> I just noticed that doing a 'J s' (gnus-agent-fetch-session) on
> sufficient large number of groups can make the gnus-newsrc-alist so
> large that you run out of memory while saving it.  I've traced the
> problem to gnus-save-newsrc-file which writes everything to a buffer
> then uses save-buffer to write it to a file.

Wow.  Is the .newsrc.eld file really that big?

Anyway, I just found a bug in the .newsrc.eld code that made my file
7k long instead of 700k, as it apparently was supposed to be.  I've
now bound print-length to nil the appropriate function.

> I'd like to rewrite gnus-save-newsrc-file to write directly to a
> temp file then, if no errors occur during writing, rename the temp
> file as .newsrc.eld.

I'm not sure it's possible to do any such thing in a reasonable
fashion.  You'd have basically to implement the Lisp writer in a
file-specific manner.

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen



  reply	other threads:[~2003-03-30  2:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24 22:30 Kevin Greiner
2003-03-30  2:23 ` Lars Magne Ingebrigtsen [this message]
2003-03-31 14:55   ` Kevin Greiner

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=m37kah7ft4.fsf@quimbies.gnus.org \
    --to=larsi@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).