Re: Gnus from CVS, Emacs from CVS --> out of memory?

[Kevin Greiner <kgreiner@xpediantsolutions.com>]

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

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

First load-library debug.
Set debug-on-error or debug-on-signal (not sure which, if either, will
work with out-of-memory).
Then try 'J s'.

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.

Kevin