This section describes some of the most common problems that can occur on any platform during installation or configuration.
On Mac OS X, Linux, x86/x64 Solaris, FreeBSD and AIX, the key is expected to be stored in a keyfile, and an appropriate error message is printed at the terminal for each case. If this message does not help you to resolve the problem, report it to Lisp Support and include the terminal output.
On Windows, the key is expected to be stored in the Windows registry. If you cannot resolve the problem, export your HKEY_LOCAL_MACHINE\SOFTWARE\LispWorks registry tree and include this with your report to Lisp Support.
A common cause of errors seen while building (delivering) an application is running part of the application's runtime initialization, or something else that assumes the application is already running.
Such initializations should be done at the start of the runtime phase, as described in Separate runtime initializations from the build phase.
<**> Failed to enlarge memory
The message means that the LispWorks image is close to the limit: it attempted to expand one of the GC generations, but there was not enough swap space to accommodate the resulting growth in image size. When this happens, the garbage collector is invoked. It will usually manage to free the required space, but if it cannot then crashes may result. Therefore you should take action to reduce allocation or increase available memory when you see this message.
Check the size of the image, both by
cl:room and by OS facilities (such as
top on *nix, Task Manager on Windows) to see if all the sizes are as expected. If there are large discrepancies, check them.
Occasionally, however, continued demand for additional memory will end up exhausting resources. You will then see the message above repeatedly, and there will be little or no other activity apparent in the image. At this point you should restart the image, or increase swap space. In cases where external libraries are mapped above LispWorks and inhibit its growth, you may be able to relocate LispWorks, as described under "Startup relocation" in the LispWorks User Guide and Reference Manual .
Programs which attempt to clean up your machine by automatically removing data they identify as unnecessary may accidentally corrupt your LispWorks executable, because they do not understand its format. This will prevent LispWorks from starting.
LispWorks Release Notes and Installation Guide - 2 Mar 2015