garbage collection

[Godmar Back]

> 
> > gback at cs.utah.edu said:
> > > Incremental gc does a bit of gc at every allocation.  Both 
> > > asynchronous and incremental gc require barriers.
> > 
> > So the garbage collector in Kaffe is currently neither incremental nor 
> > asynchronous and just kicks in when object allocation fails because of an 
> > out-of-memory condition?
> > 

Sort of.  For the details, look at gc-mem.c

> Actually, the GC doesn't seem to be doing even that, and I'm not sure if it 
> does anything at all. I increased the loop count in my sample program to 2 
> milion, and kaffe failed with the following error:
> 
> java.lang.OutOfMemoryError
>         at TestGC.main(19)
> 
> (That's the 'new' statement.) What gives?
> 

 Your example runs just fine with 2 millions for me.

	- Godmar