NetNews Usenet Archive 1992 #19/NN_1992_19.iso/spool/gnu/emacs/help/3865

Internet Message Format | 1992-08-27 | 1.7 KB

Path: sparky!uunet!bonnie.concordia.ca!hobbit.ireq.hydro.qc.ca!NetNews.ireq.hydro.qc.ca!gamin
From: [e-mail] (Martin Boyer)
Newsgroups: gnu.emacs.help
Subject: Re: memory exhausted
Message-ID: <[e-mail]>
Date: 27 Aug 92 16:40:36 GMT
References: <[e-mail]>
Sender: [e-mail] (Netnews Admin)
Distribution: na
Organization: Le laboratoire de robotique de l'Institut de recherche
    d'Hydro-Quebec
Lines: 28
In-Reply-To: [e-mail]'s message of 25 Aug 92 17:47:11 GMT

>>>>> Ron Katriel writes:

>I am getting a "memory exhausted" error message when running Lucid
>Common Lisp from within GNU Emacs 18.57.6 (aix-v3).  The problem occurs
>when the Lisp process puts out trace output in excess of 1 Megabyte to
>the *lisp* buffer.

I just had the same problem with Mathematica.  As far as I could
determine, the process buffer is simply consuming too much memory for
emacs or for the swap space on the machine.  I did three things to
save emacs from dying (the guy *wanted* the result of his 2 hour long
computation):

1. Killed all other buffers.
2. Evaluated (buffer-flush-undo (current-buffer)) in the process
   buffer.  This gets rid of all "undo" information and prevents
   accumulation of new information for that buffer.
3. Erased all text not needed in that buffer (using "delete-region",
   not "kill-region").

You may want to put (buffer-flush-undo (current-buffer)) in the proper
mode-hook. This is what the *compilation* buffer does.

--
Martin Boyer                            [e-mail]
Institut de recherche d'Hydro-Quebec    [e-mail]
Varennes, QC, Canada   J3X 1S1
[phone]