Memory deallocation question about iov_dup

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

  I am facing a big memory leak and I believe the responsible parts are the iov_dups I am doing while reading a file to write it somewhere else, because the system's memory is running out according to the file size I am dealing with.
  Before calling a WIND that needs the vector as param I do a iov_dup() to a local pointer and this goes as the WIND parameter. 

  To correctly deallocate this, the best thing is a GF_FREE after the WIND or saving the pointer to local and deallocate it at the callback? Or any other approach, like only before the UNWIND after the sequence of WINDs(where I am deallocating the local, for example)?

Thanks,
Gustavo Brand
---------------------------------------------------------------------------------

[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux