Bug 1403156 - Memory leak on graph switch
Summary: Memory leak on graph switch
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: GlusterFS
Classification: Community
Component: libgfapi
Version: mainline
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact: Sudhir D
URL:
Whiteboard:
Depends On:
Blocks: 1394229
TreeView+ depends on / blocked
 
Reported: 2016-12-09 09:53 UTC by rjoseph
Modified: 2019-04-22 06:18 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1394229
Environment:
Last Closed: 2019-04-22 06:18:23 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Comment 1 rjoseph 2016-12-09 09:54:24 UTC 
--- Additional comment from Poornima G on 2016-11-17 07:29:20 EST ---

The culprits:
- Inode table of old graph needs cleanup.
        Fix inode leaks
        Fix forget of each xl to free inode ctx properly
- The xl objects itself (xlator_t)
- The mem_accnt structure in every xl object.
        Fix all the leaks so that the ref count of mem_accnt structure is 0
- Implement fini() in every xlator
Comment 4 Yaniv Kaul 2019-04-17 12:14:12 UTC 
I believe we've done some good work overall on memory leaks, with Coverity and ASAN, clang-scan and reduction of GCC warnings. While I don't know if we fixed this specific issue, we need more focused bug.
Agreed?
Comment 5 Sahina Bose 2019-04-22 06:18:23 UTC 
Closing this. Will open specific bugs as encountered with latest version
Note You need to log in before you can comment on or make changes to this bug.