zeroshade commented on PR #14878: URL: https://github.com/apache/arrow/pull/14878#issuecomment-1347252867
To be clear: if the user is using `memory.DefaultAllocator` then it *should* free the underlying memory at some point when the GC cleans everything up. But if they are using a custom allocator of some kind, then it will not actually call Free unless `Release` is called on `w.bitsBuffer`. One thing I've been thinking of every so often is to try to leverage SetFinalizer more with the usage of the Allocators, but there are benefits to allowing users to have that granular control over *when* memory is released (well, at least when it's set to nil for the GC to pick it up) since SetFinalizer isn't guaranteed to run at any specific time. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
