[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: bug of GC "step"
- From: Makoto Hamanaka <naraxx800@...>
- Date: Sat, 05 Jul 2008 10:12:01 +0900
> yes, the correct fix is not surprisingly the one by the author, which
> is basically what you suggested. :)
> One last question: with this change, does a pause of 100 or lower mean
> "sweep everything every time the GC is checked"?
In my understanding, pause value will not affect collectgarbage("step",n),
because that setting is intended for controling the automatic GC
About the source side, that g->gcpause is only used on setthreahold()
macro. And setthreshold() macro will be called only on the end of GC
cycle, but with this change, it will just return from collectgarbage("step")
and the new threshold will not be used.
Whereas stepmul value can affect the size of GC work about one call of
It looks like, (n * m) can be a rough indication of the amount of GC
work it will do, but the unit of that value is percent or byte is not
known now ;-)
Makoto Hamanaka <firstname.lastname@example.org>