Note: set-memory-check is a more robust way to protect against memory exhaustion problems.
The number of the generation in which it was trying to allocate.
The size in bytes which it was trying to allocate.
A string naming the allocation type it was trying to allocate.
A boolean, true if it was trying to allocate a static object, and false otherwise.
function is placed first in the callbacks list.
function is placed last in the callbacks list.
function is removed from the callbacks list.
set-memory-exhausted-callback always first removes function from the callbacks list, and then adds it according to where. The default value of where is
:first. Functions in the list are compared with
When a callback is called, Lisp already failed to map memory. This means that you must not rely on the callback to do real work. It should therefore attempt only a minimal amount of work such as clean-ups and generating debug information. It should not try to do real work.
LispWorks User Guide and Reference Manual - 13 Feb 2015