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
We faced with memory leak with one of our applications, which periodically iterates over whole Rocksdb database to compute some statistics. We also use MergeOperator implemented in Go, and it turns out that the memory allocated within MergeOperator is never freed.
In file gorocksdb.c, an empty implementation of function gorocksdb_filterpolicy_delete_filter and gorocksdb_mergeoperator_delete_value preventing default function free to be called.
See rocksdb/blob/master/db/c.cc
Which may lead to memory leak.
We faced with memory leak with one of our applications, which periodically iterates over whole
Rocksdb
database to compute some statistics. We also useMergeOperator
implemented in Go, and it turns out that the memory allocated withinMergeOperator
is never freed.Please see this repository for the further infomation: https://github.com/vitalyisaev2/gorocksdb_merge_operator_issue
Picture of heap profile to grab your attention:
The text was updated successfully, but these errors were encountered: