Oleksandr Natalenko
2016-Jan-12 07:16 UTC
[Gluster-users] Memory leak in GlusterFS FUSE client
Just in case, here is Valgrind output on FUSE client with 3.7.6 + API-related patches we discussed before: https://gist.github.com/cd6605ca19734c1496a4 12.01.2016 08:24, Soumya Koduri ???????:> For fuse client, I tried vfs drop_caches as suggested by Vijay in an > earlier mail. Though all the inodes get purged, I still doesn't see > much difference in the memory footprint drop. Need to investigate what > else is consuming so much memory here.
On 01/12/2016 12:46 PM, Oleksandr Natalenko wrote:> Just in case, here is Valgrind output on FUSE client with 3.7.6 + > API-related patches we discussed before: > > https://gist.github.com/cd6605ca19734c1496a4 >Thanks for sharing the results. I made changes to fix one leak reported there wrt ' client_cbk_cache_invalidation' - - http://review.gluster.org/#/c/13232/ The other inode* related memory reported as lost is mainly (maybe) because fuse client process doesn't cleanup its memory (doesn't use fini()) while exiting the process. Hence majority of those allocations are listed as lost. But most of the inodes should have got purged when we drop vfs cache. Did you do drop vfs cache before exiting the process? I shall add some log statements and check that part Thanks, Soumya> 12.01.2016 08:24, Soumya Koduri ???????: >> For fuse client, I tried vfs drop_caches as suggested by Vijay in an >> earlier mail. Though all the inodes get purged, I still doesn't see >> much difference in the memory footprint drop. Need to investigate what >> else is consuming so much memory here.