From 361ed4fdba1a8b8ee47b7bd473161098942f0199 Mon Sep 17 00:00:00 2001 From: Luc Teirlinck Date: Mon, 29 May 2006 22:26:25 +0000 Subject: [PATCH] (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. --- lispref/internals.texi | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/lispref/internals.texi b/lispref/internals.texi index bc35e215574..fa96687d1d8 100644 --- a/lispref/internals.texi +++ b/lispref/internals.texi @@ -160,7 +160,8 @@ the preloaded libraries, @file{temacs} allocates dynamic memory for 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 @@ operating system, but which are currently not in use. (A string 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 -- 2.39.5