Re: How to debug out of memory situation?

[Richard Stallman <rms@gnu.org>]

Once you get a memory-full error in a certain session, you probably
won't learn anything more from successive memory-full errors in the
same session.  They are all secondary consequences of the first.

However, if you look at the first memory-full error in each session,
for a number of sessions, they may show a pattern that indicates
something about what code is causing the problem.

The first instance, as you reported it, is this:

"gnus-get-newsgroup-headers-xover"
"gnus-agent-fetch-group-1"
"gnus-agent-fetch-session"
"call-interactively"