Steve Elkins <firstname.lastname@example.org> writes:
> I love scsh, but I may have a problem with it.
Rest assured, you don't have. ;-)
> I say this because simply starting scsh in an xterm...
> sge:2$ scsh
> Welcome to scsh 0.6.2 (Gambit-C 4.0)
> Type ,? for help.
> ...gets me a process that grows relentlessly, 4K at a time. The one
> I'm running now has grown over 100K in < 5 minutes without my typing a
> single character into the REPL, just let it sit there. Of course this
> isn't important for the short-lived scripts I've written so far, but
> I'm hoping to use it for some more daemonish things in the future.
I think that's an OS issue. scsh allocates memory for the heap, but
the OS does not assign this memory chunk immediately.
When fired up scsh tries to allocate 10 MB, but gets less. This is
related to the memory allocation strategy of the OS. Bit by bit the OS
will assign the rest of the 10 MB in 4 k chunks to scsh (4 k is the
page size). So it should stop growing when the OS has assigned the
whole memory which scsh requested. And it does. ;-) We have a scsh
based web server (scsh.net) up and running for two months now and it
uses the same amount of memory as on the first day. ;-)
"Excuse me --- Di Du Du Duuuuh Di Dii --- Huh Weeeheeee" (Albert King)