Re: [Sbcl-help] Garbage collection for server with user sessions

[Brett v. de S. <bv...@as...>]

>On 10 March 2010 22:29, Brett van de Sande <bv...@as...> wrote:
>
>> 4.  If I run the server with the above changes, it appears that
>>    garbage collection is working as desired:  garbage collection occurs
>>    every 3 minus (generation 2), doesn't use too much cpu, and seems to
>>    be recovering the memory.  However, after about a half hour, I get a
>>    heap exhausted error.   So, I tried to increase the heap size:
>>        (def!constant dynamic-space-end         #x3ffff000)
>>    in src/compiler/x86/parms.lisp (to meet up with bottom of shared libs)
>>    This gives 922742784 bytes of heap space, instead of 500K
>>    However the heap exhaustion error still occurs, although a bit later:
>>        Heap exhausted during allocation: 234094592 bytes available,
>>        268435464 requested.
>
>As Juho noted, this is during allocation, not GC. What's the heap
>composition at this point? There should be a printout.

I am still getting this problem.  What printout am I supposed to see?
How do I find the heap composition?  At this point I just get the error
message and there is no more lisp prompt:

   Heap exhausted during allocation: 91848704 bytes available, 134217736 requested.
   CORRUPTION WARNING in SBCL pid 12955(tid 2951347088):
   Signalling HEAP-EXHAUSTED in a WITHOUT-INTERRUPTS.
   The integrity of this image is possibly compromised.
   Continuing with fingers crossed.

   debugger invoked on a SB-KERNEL::HEAP-EXHAUSTED-ERROR in thread #<THREAD
                                                                  "Hunchentoot worker (client: 127.0.0.1:38527)" RUNNING
                                                                  {D5311C1}>:
     Heap exhausted (no more space for allocation).
   There are still 91848704 bytes available; the request was for 134217736 bytes.

   PROCEED WITH CAUTION.

If I look at cat /proc/12955/maps, there seems to be an allocation
that crosses dynamic-space-end at #x3ffff000:

   ...
   2a434000-2c438000 r-xp 2a434000 00:00 0 
   2c438000-35450000 rwxp 2c438000 00:00 0 
   35450000-3d454000 rwxp 35450000 00:00 0 
   3d454000-66c00000 rwxp 3d454000 00:00 0 
   ae2fc000-ae2fd000 rwxp ae2fc000 00:00 0 
   ae2fd000-ae2fe000 r-xp ae2fd000 00:00 0 
   ae2fe000-ae5fa000 rwxp ae2fe000 00:00 0 
   ...

But I have no idea how to proceed further.

Brett