From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Memory exhausted while saving .newsrc.eld
Date: Mon, 24 Feb 2003 16:30:45 -0600 [thread overview]
Message-ID: <uk7fp8g6i.fsf@xpediantsolutions.com> (raw)
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. 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
plan on handing version-control correctly so that the new
gnus-backup-startup-file will be respected. The only problem that I
see is gnus-save-quick-newsrc-hook. This hook is currently run while
in the temporary buffer. By its documentation, you can use it to set
the buffer's version-control. Does anyone use this hook for anything
other than setting version-control? If so, I'd sure like to hear
about it.
Thanks,
Kevin
next reply other threads:[~2003-02-24 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 22:30 Kevin Greiner [this message]
2003-03-30 2:23 ` Lars Magne Ingebrigtsen
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=uk7fp8g6i.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).