[Nfd-dev] Memory leak with NFD.

Junxiao Shi shijunxiao at email.arizona.edu
Tue May 3 07:42:49 PDT 2016

Hi Anil

The call stack in the Valgrind report indicates that you are running NFD
within ndnSIM.
#3236 is fixed in NFD commit 9c903e063ea8bdb324a421458eed4f51990ccd2c on
Oct 04, 2015. However, ndnSIM's NFD fork is dated back on Aug 21, 2015, and
doesn't contain the fix.
You may try to backport that commit to ndnSIM's NFD fork, or ask ndnSIM
developers to upgrade their fork.

Yours, Junxiao

On Mon, May 2, 2016 at 5:23 PM, Anil Jangam <anilj.mailing at gmail.com> wrote:

> Hi Junxiao,
> I am observing a memory leak with NFD and to verify the same I did couple
> of Valgrind enabled simulation runs with 25 and 50 nodes. Based on the
> Valgrind report, and output of 'top' command, I see that RAM consumption
> grows consistently and rapidly. My scaling test is affected that I am not
> able to run the simulation for longer time and/or with high number of
> nodes. Also, I see a very high number of timeouts
> I see a NFD leak issue in closed state, which confirms this leak however
> closed owing to its small size. Perhaps this is showing up a high scale?
> http://redmine.named-data.net/issues/3236/
> Please check the attached Valgrind report. Let me know what other data you
> may need to debug this further. Also, please suggest a solution or
> workaround to this?
> /anil.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20160503/6ed9fe9d/attachment.html>

More information about the Nfd-dev mailing list