I am running SBCL 1.0.51 on a Linux (Fedora 15) 32-bit system (kernel 3.6.5) with 1GB Ram and 256MB swap space.

I fire up "sbcl --dynamic-space-size 125" and start calling a function that makes ~10000 http-requests (using drakma) to an http (couchDB) server and I just format to the standard-output the results of an operation on the returned data. 

After each call I do a "(sb-ext:gc :full t)" and then "(room)". The results are not growing. No matter how many times I run the function, (room) reports the same used space (with some ups and downs, but around the same average which does not grow). 

BUT: After every time I call the function, top reports that the VIRT and RES amount of the sbcl process keeps growing ,even beyond the 125MB space I told sbcl to ask for itself. So I have the following questions:


 1. Why top - reported memory keeps growing, while (room) says it does not? The only thing I can think of is some leakage through ffi. I am not directly calling out with ffi but maybe some drakma dep does and forgets to free its C garbage.  Anyway I dont know if this could even be an explanation. Could it be something else? Any insights as to where I should start searching? 
 2. Why isnt --dynamic-space-size honoured?

Thank you,
Bill