It might be a bit tricky to really make it generic, because some variables keep pointer to shared memory, definitely is not going to work for $shv(...) to be (re-)initialized after forking. So if a shv is used not very often and destroyed, then it becomes unusable for ever, (re-)initialisation will not make it properly visible to all processes. Then I am not sure that every PV does a full clean on destroy of their internal structure, so it can still leak. That's also a reason now is done for sht, because its destroy was reviewed to be clean.

So, likely you have to combine with a list of variable types that are ok for last-access-based destroy and (re-)initialise.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.