hi Kaleb,
I went through the logs. I don't see anything significant. What
is the test case that recreates the mem-leak? May be I can try it on my
setup and get back to you?
Pranith
On 10/15/2014 08:57 PM, Kaleb S. KEITHLEY wrote:
As mentioned in the Gluster Community Meeting on irc
Mine is caused with qcow2 images used by kvm on a fuse mount. About a
half dozen very busy images causes the leak pretty consistently.
Apparently, though I never got a chance to check it myself or collect
any details, we had jira building and tearing down VM images, also on a
fuse mount,
As mentioned in the Gluster Community Meeting on irc today, here are the
glusterfs client side valgrind logs. By 'glusterfs client side' I
specifically mean the glusterfs fuse bridge daemon on the client.
http://download.gluster.org/pub/gluster/glusterfs/dynamic-analysis/valgrind-3.4-memleak/
