Gnus development mailing list
 help / color / mirror / Atom feed
From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: Gnus from CVS, Emacs from CVS --> out of memory?
Date: Tue, 13 May 2003 17:13:30 +0200	[thread overview]
Message-ID: <84n0hqanhh.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <uel33hr8x.fsf@xpediantsolutions.com>

Kevin Greiner <kgreiner@xpediantsolutions.com> writes:

> 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.

ibuffer wasn't enlightening, but now I did this:

ELISP> (mapcar (lambda (b) (cons b (buffer-size b))) (buffer-list))
((#<buffer *ielm*> . 124)
 (#<buffer  *Minibuf-1*> . 0)
 (#<buffer *scratch*> . 581)
 (#<buffer *Group*> . 6551)
 (#<buffer drafts/*sent posting on gnu.emacs.help*> . 873)
 (#<buffer *sent posting on gnu.emacs.gnus*> . 2244)
 (#<buffer *Dead Summary nnimap+du:teach.infoa.mailto*> . 68)
 (#<buffer *sent reply to info dan*> . 621)
 (#<buffer *sent followup to Wang Yin on gnu.emacs.help*> . 841)
 (#<buffer *sent followup to Nacho on gnu.emacs.gnus*> . 2212)
 (#<buffer *Article*> . 241)
 (#<buffer *sent posting on gnu.emacs.help*> . 564)
 (#<buffer *sent followup to Paul Stevenson on gnu.emacs.gnus*> . 1153)
 (#<buffer *sent posting on teach.infoa*> . 527)
 (#<buffer  *Minibuf-0*> . 0)
 (#<buffer *Messages*> . 9607)
 (#<buffer  *Echo Area 0*> . 8)
 (#<buffer  *Echo Area 1*> . 19)
 (#<buffer  *nntpd*> . 2482)
 (#<buffer  *Gnus agent overview*> . 32349)
 (#<buffer  *gnus work*> . 28)
 (#<buffer  trace of POP session to mail.gmx.net> . 157)
 (#<buffer  trace of POP session to pop-serv1.uni-duisburg.de> . 173)
 (#<buffer  *nnimap* dtm> . 0)
 (#<buffer  *nnimap* du> . 0)
 (#<buffer  *server news.freshmeat.net nntp  *nntpd**> . 0)
 (#<buffer  *code-converting-work*> . 29)
 (#<buffer .bbdb> . 213373)
 (#<buffer  *Original Article*> . 1094)
 (#<buffer  *Async Prefetch Article*> . 0)
 (#<buffer  *canonical address*> . 16)
 (#<buffer  *extract address components*> . 24)
 (#<buffer  *split*> . 0)
 (#<buffer  *gnus article copy*> . 1094)
 (#<buffer  *Gnus Backlog*> . 2350948)
 (#<buffer *Completions*> . 183)
 (#<buffer  *server news.uni-duisburg.de nntp  *nntpd**> . 271)
 (#<buffer  *server news.cis.dfn.de nntp  *nntpd**> . 955)
 (#<buffer  *server news.gnus.org nntp  *nntpd**> . 2601)
 (#<buffer  *server news.gmane.org nntp  *nntpd**> . 1186)
 (#<buffer *Quail Completions*> . 0)
 (#<buffer  *nnmail message-id cache*> . 270109)
 (#<buffer .newsrc-dribble> . 586116)
 (#<buffer *Warnings*> . 68)
 (#<buffer *Help*> . 189))

I did `J s' in a Gnus.  It told me it's out of memory and asked me
whether to continue.  I said no, and then evaled the above snippet.

It doesn't look dangerous to me.  What is going on here?

How can I investigate further?
-- 
This line is not blank.



  reply	other threads:[~2003-05-13 15:13 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 [this message]
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=84n0hqanhh.fsf@lucy.is.informatik.uni-duisburg.de \
    --to=kai.grossjohann@gmx.net \
    /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).