Possible memory leak in index/store/forestdb/iterator.go

[tleyden]

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.

[mschoch]

Yes this looks like a bug.

[tleyden]

Related (closed) issue for secondary indexing: https://issues.couchbase.com/browse/MB-14701