I am using cmucl for the creation of a large graphic image (interfaced 
through the alien functions with Intels opencv and IPP libraries).  The 
program works fine for images less than 40 megabytes, but when I try to 
do something larger than this (essentially I just change the size of the 
drawing), it silently fails and returns me to the operating system.  I 
am not sure how to go about debugging this.  Flailing around, I thought 
it might be the "dynamic space" so I put in to print it out.  It starts 
out with:

+++++++++++++++++
Saving image....Radius = 991. far-corner: 10548.
*************************** trying gc ********************
Dynamic Space Usage:    75,556,648 bytes.
Read-Only Space Usage:  18,521,896 bytes.
Static Space Usage:      2,343,808 bytes.
Control Stack Usage:           740 bytes.
Binding Stack Usage:            96 bytes.
The current dynamic space is 0.
Garbage collection is currently enabled.

Breakdown for dynamic space:
   56,358,720 bytes for 7,044,840 cons objects.
   37,719,272 bytes for   742,976 instance objects.
   10,613,408 bytes for    36,313 simple-vector-type objects.
   10,453,200 bytes for    56,587 simple-array-unsigned-byte-32-type 
objects.
    6,617,192 bytes for   197,561 other objects.
   121,761,792 bytes for 8,078,277 dynamic objects (space total.)
; Compiling LAMBDA (#:G1332 #:G1333 #:G1334):
; Compiling Top-Level Form:

+++++++++++++++++
Saving image....Radius = 1415. far-corner: 10548.
*************************** trying gc ********************
Dynamic Space Usage:    71,875,792 bytes.
Read-Only Space Usage:  18,521,896 bytes.
Static Space Usage:      2,343,808 bytes.
Control Stack Usage:           740 bytes.
Binding Stack Usage:            96 bytes.
The current dynamic space is 0.
Garbage collection is currently enabled.

Breakdown for dynamic space:
   74,401,080 bytes for 9,300,135 cons objects.
   37,556,264 bytes for   740,528 instance objects.
    9,324,256 bytes for    32,846 simple-vector-type objects.
    8,870,320 bytes for    48,589 simple-array-unsigned-byte-32-type 
objects.
    6,453,776 bytes for   180,527 other objects.
   136,605,696 bytes for 10,302,625 dynamic objects (space total.)
; Compiling LAMBDA (#:G1335 #:G1336 #:G1337):
; Compiling Top-Level Form:
Loading names of the image files ....
3000. Image files loaded starting at 3001..
Reversing title table....

...................................
And it continues like this until it gives the following and subsequently 
fails:



+++++++++++++++++
Saving image....Radius = 5448. far-corner: 10548.
*************************** trying gc ********************
Dynamic Space Usage:    121,898,656 bytes.
Read-Only Space Usage:  18,521,896 bytes.
Static Space Usage:      2,343,808 bytes.
Control Stack Usage:           740 bytes.
Binding Stack Usage:            96 bytes.
The current dynamic space is 0.
Garbage collection is currently enabled.

Breakdown for dynamic space:
   65,836,248 bytes for 1,289,872 instance objects.
   28,674,176 bytes for 3,584,272 cons objects.
   15,998,736 bytes for    51,304 simple-vector-type objects.
   15,949,208 bytes for    85,808 simple-array-unsigned-byte-32-type 
objects.
    7,947,776 bytes for   254,837 other objects.
   134,406,144 bytes for 5,266,093 dynamic objects (space total.)
; Compiling LAMBDA (#:G1572 #:G1573 #:G1574):
; Compiling Top-Level Form:
; Compiling LAMBDA (#:G1575 #:G1576 #:G1577 #:G1578 #:G1579 #:G1580):
; Compiling Top-Level Form:
; Compiling LAMBDA (#:G1581 #:G1582 #:G1583 #:G1584 #:G1585 #:G1586 
#:G1587 #:G1588):
; Compiling Top-Level Form:
[EMAIL PROTECTED] tiha]$


The saved file at this point is about 40 megabytes.  Does anyone have 
any recommendations about how to investigate this problem further?  I am 
running Redhat 8.0 with 1 gigabyte of ram on a xeon 2.4meghz processor 
with plenty of disk space
thanks
Blake


Reply via email to