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
I've recently discovered that if a doc returned from calling iterator.Get() is not explicitly closed, it can result in memory leak -- see google groups thread
Reading over the code in index/store/forestdb/iterator.go, it's not obvious to me that this resource leak is avoided, since there is never an explicit call to doc.Close(). From my observations, even if the reference to the Go wrapper doc is GC'd, the underlying cgo memory won't be released.
I haven't observed any bugs while using bleve, this was just from reading index/store/forestdb/iterator.go, so there's a good chance it's not really a bug.
The text was updated successfully, but these errors were encountered:
I've recently discovered that if a doc returned from calling iterator.Get() is not explicitly closed, it can result in memory leak -- see google groups thread
Reading over the code in index/store/forestdb/iterator.go, it's not obvious to me that this resource leak is avoided, since there is never an explicit call to doc.Close(). From my observations, even if the reference to the Go wrapper doc is GC'd, the underlying cgo memory won't be released.
I haven't observed any bugs while using bleve, this was just from reading index/store/forestdb/iterator.go, so there's a good chance it's not really a bug.
The text was updated successfully, but these errors were encountered: