Closed tmadlener closed 1 year ago
This should fix #500 (still have to test that on a larger scale) but it is a bit cumbersome and the "proper" solution would be to make the CollectionReadBuffers
owners of their data and giving them move-only semantics such that the flow of ownership of the data is expressed much more clearly.
I would be happy to merge this as is to fix the current leak and then address the "proper" solution after v1.0, because I am not entirely sure whether it can be made to work with the EventStore.
Is it WIP or are you finished with this now? I am asking because of more commits coming in. Thanks
Just finished a few more larger scale tests and valgrind and this fixes the leaks of unconsumed collection buffers.
BEGINRELEASENOTES
deleteBuffers
function that is populated at generation time to theCollectionReadBuffers
to make it possible to dispose of unconsumed buffers. This fixes the main leaks described in #500ROOTFrameData
clean up all unconsumed buffers at desctruction.ENDRELEASENOTES
Fixes #500