[Bugs] [Bug 1287517] Memory leak in glusterd

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1287517



--- Comment #37 from Gaurav Kumar Garg <ggarg at redhat.com> ---
hi roman,

there is one update regarding this.

if by looking into glusterd log's you are saying that memory allocated by
glusterd_set_txn_opinfo call too many number of time compare to
glusterd_clear_txn_opinfo then its wrong. its true that glusterd_set_txn_opinfo
calling more number of time at remote node compare to glusterd_clear_txn_opinfo
but it doesn't mean that every time its allocate memory. from the function
(glusterd_set_txn_opinfo) you can see that if ret is non zero (means its unable
to get txn opinfo from the dictionary) then only it will allocate memory and it
happen only one's at the starting of transaction. 


if you apply http://review.gluster.org/12927 patch at all the node in the
cluster then you will see only few byte of memory leak. 

i am checking it further why few byte of memory leak happening. will update you
further.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=yTLPvdZtUx&a=cc_unsubscribe