You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MB-41321: 2/4 Clean-up if collection exists in old and new drop containers
Collections::Flush was erasing a collection from the new drop 'map'
when it was found to be in both 'old' and 'new' - this is so the
flatbuffer output (which is a vector) only had the dropped collection
once.
However this leads to code executing later in the flush to not see
the collection when iterating through the 'droppecCollections' map.
For example notifyManifestOfAnyDroppedCollections would not get the
VB::Manifest to clean-up (effectively leaking memory).
This fix ensures we still generate the collection once in the
flatbuffers output, but also keep it in the list and now clean-up.
Change-Id: I3f9f91ee34b82a748e8145b70a4ce47089ad3687
Reviewed-on: http://review.couchbase.org/c/kv_engine/+/137698
Tested-by: Build Bot <[email protected]>
Reviewed-by: Dave Rigby <[email protected]>
0 commit comments