TLDR: Is there any way to reasonably write test cases to test finalizer behaviors?
I'm trying to implement a memory-sensitive canonicalizing map / cache in Go. Since there is no notion of "soft reference" (and because my object graph will always form a DAG), I'm accomplishing this with a tiny interface/framework that tracks counts of references in the userland:
type ReferenceCounted interface {
RefCount() int
IncRef()
DecRef() (bool, error)
}
type Finalizable interface {
ReferenceCounted
Finalize()
}
type AbstractCounted struct {
// unexported fields
}
The way this works is that you have a struct which embeds AbstractCounted, and implement Finalizable.Finalize()
- these together make that struct receive the Finalizable
interface. Then there is a function func MakeRef(obj Finalizable) *Reference
which returns a pointer to a struct which receives a method func Get() Finalizable
, which gets the reference target, and which is initialized by incrementing the ref count on the unerlying object, then setting a finalizer (via runtime.SetFinalizer()
) which will decrement the reference. AbstractCounted
's Finalizable
implementation in turn calls Finalize()
on the struct which embeds it when the ref count reaches zero.
So, everything is set up to work very much like soft references / ref queues in Java would now, with the exception that it's reference counting and not a mark/sweep rooted in active lexical scopes that is finding things "softly" reachable.
It seems to work great! But - I would like to write a test case...
I understand fully that finalizer invocation is deferred, and that no guarantees are made about running them per the reflect
package docs. The situation is the same in other languages with runtime gc and finalizers (C#, VB, Java, Python, etc) as well.
However, in all of those other languages, requesting explicit GC (here through the runtime.GC()
function) does seem to cause finalizers to get run. Since that's not the case in Go, I cannot figure out a way to write a test case that will trigger the finalizers.
Is there any trick or code fragment (I'm OK with this being current-implementation dependent, ie. could-break-in-future!) that will reliably trigger those finalizers so I can write my test?