Gisle S�lensminde wrote:
>
> When I was loading a database of biological sequences into memory, I got
> the following error message:
>
> ------------ BEGIN ERROR MESSAGE ------------------------------
>
> *A1 gc_alloc_large failed, nbytes=50518704.
> CMUCL has run out of dynamic heap space (512 MB).
> You can control heap size with the -dynamic-space-size commandline
> option.
>
[snip]
> -------------- END ERROR MESSAGE ------------------------------
>
> I followd the advice from the error message, and increased the dynamic
> space size to 1GB (101037408 Bytes). Still it crashes when it exeeds
> 512MB. Is this a hardcoded limit to CMUCL. Im using 19a.
I can't reproduce this with 19a on my Suse 9 box:
19a $ bin/lisp -noinit -dynamic-spe-size 800
* (defvar *s* (make-array 350000000 :element-type '(signed-byte 16)))
*S*
* (room)
Dynamic Space Usage: 700,350,920 bytes (out of 800 MB).
Read-Only Space Usage: 20,054,376 bytes (out of 256 MB).
Static Space Usage: 2,907,616 bytes (out of 256 MB).
Control Stack Usage: 484 bytes (out of 128 MB).
Binding Stack Usage: 96 bytes (out of 128 MB).
The current dynamic space is 0.
Garbage collection is currently enabled.
Breakdown for dynamic space:
700,000,008 bytes for 1 simple-array-signed-byte-16-type
object.
407,800 bytes for 42,951 other objects.
700,407,808 bytes for 42,952 dynamic objects (space total.)
We'll need more information to figure this out.
Ray
