procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

(Pure Storage): Mention that an overflow in pure

Browse source 
space causes a memory leak.
(Garbage Collection): If there was an overflow in pure space,
`garbage-collect' returns nil.
This commit is contained in:
Luc Teirlinck 2006-05-29 22:26:25 +00:00
parent 93fd6289fe
commit 361ed4fdba
1 changed files with 6 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
lispref/internals.texi
View file

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