Thanks...that must be it.  I was thinking that IGC was triggered by
exceeding an object allocation threshold, but in this case it must be
getting triggered more often by running low on space...it seems that IGC
must be freeing up enough space for the object allocation that triggered
it and not growing memory (as I was thinking it would)...and because
it's not growing memory it's running low on space again and again.  Is
there some way that this (that the VM keeps doing IGCs because of low
space as opposed to reaching the allocation threshold) could be
detected?

- Stephen

> -----Original Message-----
> From: squeak-dev-admin at lists.squeakfoundation.org 
> [mailto:squeak-dev-admin at lists.squeakfoundation.org] On 
> Behalf Of Tim Rowledge
> Sent: Wednesday, August 28, 2002 5:31 PM
> To: squeak-dev at lists.squeakfoundation.org
> Subject: Re: GC behavior?
> 
> 
> The instant response from my subconscious (the only part 
> working right now, headcold has turned off all higher 
> functions) is that you might simply be making use of more 
> _space_ now that you have bigger headers. It's a tenuous 
> suggestion but ought to be easy to check. Bigger headers 
> implies fewer objects in the same amount of memory, implies 
> more frequent incremental gc. Sanity checking arithmetic left 
> to the reader...
> 
>  tim
> -- 
> Tim Rowledge, tim at sumeru.stanford.edu, 
> http://sumeru.stanford.edu/tim Strange > OpCodes: SNARF: System 
> Normalize And Reset Flags
> 
> 
>