This repository was archived by the owner on Apr 24, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 24, 2026. It is now read-only.
Memory leak when mounting volumes? #14
Description
Is there a memory leak in the API? Running the script below from the python interpreter results in a very high memory usage that stays high until exiting the python interpreter.
#foo.py
from gluster.gfapi import Volume
def main():
for _ in xrange(20):
v = Volume("master", "glustervolume")
v.mount()
v.umount()
if __name__ == "__main__":
main()
This can also be seen using the vprof memory profiler
$ vprof -c cmh -s bar.py
Or am I missing something?
Activity
prashanthpai commentedon Jul 1, 2016
@OskarPersson This is a known issue present in the libgfapi C library. The python-bindings cannot do much here to do the cleanup. Freeing up all the resources during unmount is intricate and complex. It was addressed to some extent earlier and has improved over time. However there are further residual cleanups that needs to be done.
prashanthpai commentedon Aug 11, 2016
@OskarPersson Many consumers of libgfapi C library (Samba, NFS ganesha) usually do mount once and consume the same session for all subsequent I/O operations. May I know whether your actual application workflow intends to mount and unmount multiple times ?