I am running a long-duration testing for my Java application that uses the FDB Java Binding Library to access the FDB backend. My version of the FDB backend is 6.0.15 and the Java Library is with 6.0 correspondingly. I just found that over the 9-hour window, the VM container running my Java application process (only 1 process in one VM container) has the memory residential memory (RSS) increased over 8 GB and thus reaches the container’s memory limit and then gets killed by the VM container manager. Though I am still investigating where the memory leaking comes from, I found that there is a FDB release note, https://apple.github.io/foundationdb/old-release-notes/release-notes-200.html, and there is a section on “Java” in it, which states “Fix: calling getRange on a Transaction could leak memory”. In fact, all of my application’s access to the FDB backend is via “getRange” queries. So I would like to see whether this is really the problem that I run into.
(1) Is this the bug that has been there in FDB 6.0.15 already?
(1) could you describe under what circumstance the memory leak can happen for getRange?
(2) could you point me to the PR that is related to this particular fix, in FDB 6.1*, and in Both Java and in the Client Library (likely), so that I can check whether my code does run into this memory leak problem?