Bug 1369703 - memory leak caused by client_uid
Summary: memory leak caused by client_uid
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: locks
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Susant Kumar Palai
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-24 08:00 UTC by Ryan Ding
Modified: 2018-08-29 03:35 UTC (History)
2 users (show)

Fixed In Version: glusterfs-4.1.3 (or later)
Clone Of:
Environment:
Last Closed: 2018-08-29 03:35:21 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Ryan Ding 2016-08-24 08:00:23 UTC 
Description of problem:

features/locks xlator will leak memory after lock/unlock test.

Steps to Reproduce:

1. run lock/unlock test on fuse client (I use ltp's fs testcase, it include a lot file lock operation)
2. run for a while, use kill -s SIGUSR1 to see the memory usage. it will show like:

[features/locks.test_gfs-locks - usage-type gf_common_mt_strdup memusage]
size=66391322
num_allocs=1070830
max_size=66391322
max_num_allocs=1070830
total_allocs=1071338

a lot strdup memory have not been released.
Comment 1 Worker Ant 2016-08-24 08:16:17 UTC 
REVIEW: http://review.gluster.org/15303 (features/locks: fix memory leak caused by client_uid) posted (#1) for review on master by Ryan Ding (ryan.ding)
Comment 2 Amar Tumballi 2018-08-29 03:35:21 UTC 
This update is done in bulk based on the state of the patch and the time since last activity. If the issue is still seen, please reopen the bug.
Note You need to log in before you can comment on or make changes to this bug.