Sometimes Allegro CL, particularly with large images, run out of memory with a storage-condition. Why might this be happening?
The most common cause of this problem is that you’ve run out of address space for the lisp heap. The first question to ask yourself, as a developer, is: Do I expect my application to consume as much memory at is it? If the question is no, you should determine the cause of the unexpected allocations and resultant heap growth. The Space Analyzer can help you do so. If the answer is yes, then it may be that you need to adjust the locations of the heaps used by Allegro CL. Choosing an adequate location in which to map the Lisp and foreign (C) heaps in a running Lisp image is complex. We refer to these problems collectively as the heap placement problem. While these problems are not in fact new, they are only triggered when the Lisp image is large (typically greater than 500 Mbytes). Continue reading the questions below for advice on how to proceed.
Related Questions
- Sometimes Allegro CL, particularly large images, run out of memory or fail totally with a bus error or a segv. Why might this be happening?
- Sometimes Allegro CL, particularly with large images, run out of memory with a storage-condition. Why might this be happening?
- Sometimes Allegro CL, particularly with large images, fail totally with a bus error or a segv. Why might this be happening?
