changeset 71077:e610fb70748a

(Pure Storage): Mention that an overflow in pure space causes a memory leak. (Garbage Collection): If there was an overflow in pure space, `garbage-collect' returns nil.
author Luc Teirlinck <teirllm@auburn.edu>
date Mon, 29 May 2006 22:26:25 +0000
parents 495e2dcf9392
children e917fe503f6c
files lispref/internals.texi
diffstat 1 files changed, 6 insertions(+), 1 deletions(-) [+]
line wrap: on
line diff
--- a/lispref/internals.texi	Mon May 29 22:23:38 2006 +0000
+++ b/lispref/internals.texi	Mon May 29 22:26:25 2006 +0000
@@ -160,7 +160,8 @@
 the part that didn't fit.  If that happens, you should increase the
 compilation parameter @code{PURESIZE} in the file
 @file{src/puresize.h} and rebuild Emacs, even though the resulting
-image will work.  Such an overflow normally won't happen unless you
+image will work: garbage collection is disabled in this situation,
+causing a memory leak.  Such an overflow normally won't happen unless you
 try to preload additional libraries or add features to the standard
 ones.  Emacs will display a warning about the overflow when it
 starts.
@@ -348,6 +349,10 @@
 object consists of a header and the storage for the string text
 itself; the latter is only allocated when the string is created.)
 @end table
+
+If there was overflow in pure space (see the previous section),
+@code{garbage-collect} returns @code{nil}, because a real garbage
+collection can not be done in this situation.
 @end deffn
 
 @defopt garbage-collection-messages