search

ravthan / all-eyes

Automatically exported from code.google.com/p/all-eyes
0 stars 0 forks source link

possible memory leak #91

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Even though 'ae' daemon code never dynamically allocates memory, when we run it 
through valgrind over 12 hours or so and terminate the execution, we receive a 
message from valgrind stating there is some memory loss.

This should be debugged further,
ravi.

Original issue reported on code.google.com by ravt...@gmail.com on 20 Nov 2012 at 2:13

GoogleCodeExporter commented 8 years ago 

After the latest fixes, ran ae daemon for 20+ hours and didn't see any memory 
leak.  So, marking it fixed,
ravi.

Original comment by ravt...@gmail.com on 28 Nov 2012 at 8:35

GoogleCodeExporter commented 8 years ago 
Verified with unit testing

Original comment by tbrt....@gmail.com on 9 Dec 2012 at 9:24