: witness exhausted
Am I leaking something? Or is the witness code? I looked at
subr_witness.c, and I don't see witness_free() being called from
witness_destroy(). There's probably some design constraint that
I don't understand.
Unfortunately dead witnesses may still be stuck in the lock order
John Baldwin writes:
Unfortunately dead witnesses may still be stuck in the lock order
hierarchy and I haven't figured out yet how to properly handle the
case of free'ing a witness structure from the tree while preserving
the correct lock orders. You can try
Ah, I think I see.
I'm developing a character driver which tracks a lot of state on a
per-open basis. I've got several mutexes in there which are
initialzed at open, and destroyed at close. After a few
dozen opens, witness seems to croak with:
witness_get: witness exhausted
Am I leaking something
