Description of problem: This talks about some obvious memory leaks, which can be cleaned up in the snapshot code path. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
REVIEW: http://review.gluster.org/15668 (snapshot: Fix for memory leaks in snapshot code path) posted (#1) for review on master by Avra Sengupta (asengupt)
REVIEW: http://review.gluster.org/15668 (snapshot: Fix for memory leaks in snapshot code path) posted (#2) for review on master by Avra Sengupta (asengupt)
REVIEW: http://review.gluster.org/15668 (snapshot: Fix for memory leaks in snapshot code path) posted (#3) for review on master by Avra Sengupta (asengupt)
COMMIT: http://review.gluster.org/15668 committed in master by Rajesh Joseph (rjoseph) ------ commit 48a4c4e525665115f7e8c478d3bf51764427378d Author: Avra Sengupta <asengupt> Date: Tue Oct 18 12:52:36 2016 +0530 snapshot: Fix for memory leaks in snapshot code path Change-Id: Idc2cb16574d166e3c0ee1f7c3a485f1acb19fc8c BUG: 1386088 Signed-off-by: Avra Sengupta <asengupt> Reviewed-on: http://review.gluster.org/15668 NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Smoke: Gluster Build System <jenkins.org> Reviewed-by: Rajesh Joseph <rjoseph>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.10.0, please open a new bug report. glusterfs-3.10.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/gluster-users/2017-February/030119.html [2] https://www.gluster.org/pipermail/gluster-users/