[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Lua 5.1(work4) collection query
- From: Chris Chapman <canis.lupus@...>
- Date: Thu, 27 Jan 2005 19:58:21 +0000
Indeedy. Forcing g->gcgenerational to be 0 all the time in the
"atomic" function allows the collector to do its job.
Thanks for the pointer - I couldn't find any reference to that in the
archives, but then the archive is a little hard to navigate for me.
On Thu, 27 Jan 2005 19:04:28 +0000, Adam D. Moss <email@example.com> wrote:
> Chris Chapman wrote:
> > The reason I ask is that the behaviour I'm seeing from the lua VM is
> > that the GCthreshold remains constant at some high value, even though
> > the garbage collector has been through several sweeps. If I call
> > lua_gc and make it do a full (non-incremental) collect, it manages to
> > clear up all of the collectable data. If I don't do a full collect,
> > the data is never collected. No combination of parameters to SETPACE,
> > SETINCMODE or STEP seems to make a difference.
> IIRC the last time a GC discussion popped up we vaguely established
> that there's something mysteriously wrong with the generational
> collection. If generational collection if disabled (which requires
> a small code change) then you can still allow incremental
> collection etc. but you might find things more to your liking.
> Adam D. Moss . ,,^^ firstname.lastname@example.org http://www.foxbox.org/ co:3