mmaul / clml

Common Lisp Machine Learning Library
Other
261 stars 36 forks source link

Heap exhaustion during installation on SBCL with 16GB heap #50

Closed lukego closed 3 years ago

lukego commented 3 years ago

I am not able to install CLML due to heap exhaustion on SBCL. I have increased the heap size to the recommended level and then far beyond (up to 4GB, then 8GB, then 16GB.)

Anyone have an idea what might be wrong?

CL-USER> (load "/home/luke/quicklisp/setup.lisp")
T
CL-USER> (ql:quickload :clml)
To load "clml":
  Load 1 ASDF system:
    clml
; Loading "clml"
..................................................
...........................
Heap exhausted during garbage collection: 0 bytes available, 32 requested.
Gen  Boxed   Code    Raw  LgBox LgCode  LgRaw  Pin       Alloc     Waste        Trig      WP GCs Mem-age
 1   91142      0  65813      0      0      0   15  5142474288    627152   171798691  156955   0  1.0023
 2  141580      2  77750     89      0    209  139  7065754944 131080896     2000000  219630   0  0.0000
 3       0      0      0      0      0      0    0           0         0     2000000       0   0  0.0000
 4       0      0      0      0      0      0    0           0         0     2000000       0   0  0.0000
 5       0      0      0      0      0      0    0           0         0     2000000       0   0  0.0000
 6     432      2    182     55      0     10    0    21643664    671344     2000000     681   0  0.0000
 7   84518      0  62504      0      0      0    0  4817162816    454080     2000000  147022   0  0.0000
           Total bytes allocated    =   17047035712
           Dynamic-space-size bytes =   17179869184
GC control variables:
   *GC-INHIBIT* = true
   *GC-PENDING* = true
   *STOP-FOR-GC-PENDING* = false
fatal error encountered in SBCL pid 271251 tid 271263:
Heap exhausted, game over.

Error opening /dev/tty: No such device or address
Welcome to LDB, a low-level debugger for the Lisp runtime environment.
ldb> 
lukego commented 3 years ago

Sorry, very likely false alarm, I did not take my .sbclrc into account which forces DEBUG 3 and SAFETY 3 which is most probably behind this!