Bug 1065312 - nfs+nlm: memory leak with locks
Summary: nfs+nlm: memory leak with locks
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: gluster-nfs
Version: 2.1
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Niels de Vos
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-14 10:42 UTC by Saurabh
Modified: 2016-01-19 06:14 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-03 17:14:40 UTC
Embargoed:


Attachments (Terms of Use)
valgrind (512.66 KB, text/x-log)
2014-02-14 10:42 UTC, Saurabh
no flags Details

Description Saurabh 2014-02-14 10:42:21 UTC
Created attachment 863214 [details]
valgrind

Description of problem:
tried to collet memory leak information using valgrind tool
on the mount point executed cthon lock tests.

Version-Release number of selected component (if applicable):
glusterfs-3.4.0.59rhs-1.el6rhs.x86_64

How reproducible:
seen on this build

Steps to Reproduce:
1. put the nfs process with valgrind, to check the memory leak
2. mount the volume
3. start cthon lock tests

Actual results:
==3788== LEAK SUMMARY:
==3788==    definitely lost: 517,304 bytes in 15,244 blocks
==3788==    indirectly lost: 3,088 bytes in 45 blocks
==3788==      possibly lost: 12,476 bytes in 72 blocks
==3788==    still reachable: 247,439,092 bytes in 2,261 blocks
==3788==         suppressed: 0 bytes in 0 blocks


Expected results:
no leaks.

Additional info:

Comment 2 Vivek Agarwal 2015-12-03 17:14:40 UTC
Thank you for submitting this issue for consideration in Red Hat Gluster Storage. The release for which you requested us to review, is now End of Life. Please See https://access.redhat.com/support/policy/updates/rhs/

If you can reproduce this bug against a currently maintained version of Red Hat Gluster Storage, please feel free to file a new report against the current release.


Note You need to log in before you can comment on or make changes to this bug.