Re: memory allocation problem

>> Memory allocation problem: An allocation request for 262160 bytes
>> caused a need for 56623104 more bytes of heap.
> 
> Hi,
> 
> but why allocating 256 kilobytes requires 56 MEGABYTES of heap? Is it
> a misleading message or something weird in the garbage collector?
> 
> David

See gc.htm. In particular the gsgc parameters :free-percent-new,
:expansion-free-perent-new, and :expansion-free-percent-old.

When it is necessary to grow the heap, the garbage collector will
attempt to grab some amount of free space as well so that a GC is not
required after every new allocation. The default for the :expansion-*
parameters is 35%, which means you'll start seeing space requests for
many megabytes once your heap reaches a few hundred MBs in size.

storage-allocation failures are usually indicative of a need to better
layout the heaps in the address space, followed by some tuning of
the garbage collector. 

Mikel Bancroft		[email protected]		http://www.franz.com/
Franz Inc., 555 12th St., Suite 1450, Oakland, CA  94607, USA
Phone: (510) 452-2000	FAX: (510) 452-0182