[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-users] set-finalizer! and cons
From: |
felix winkelmann |
Subject: |
Re: [Chicken-users] set-finalizer! and cons |
Date: |
Mon, 23 Jan 2006 08:23:12 +0100 |
On 1/21/06, Zbigniew <address@hidden> wrote:
> I've thought about this some more, and I guess I don't fully
> understand it after all. Given a pending-finalizer buffer size of
> XXX, using the -:fXXX option, simply having more than XXX live
> finalizers forces a major GC every time a new finalizer is created.
> None of these finalizers are pending, so why does the pending buffer
> size come into play? Is this simply a pathological case which cannot
> be fixed without increasing the pending buffer? Are we constrained by
> the total number of finalizers irrespective of how many are live or
> pending invocation?
The runtime system doesn't know at that time how many of the
finalizers will become free after the next GC, so it conservatively
forces a GC in the hope of releasing some of them.
cheers,
felix