Hi all, I check that simple script by valgrind.
root@linux-7qs3:[workspace] [] $ valgrind --leak-check=full ./script ==2274== Memcheck, a memory error detector ==2274== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al. ==2274== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copyright info ==2274== Command: ./script ==2274== ^C==2274== ==2274== HEAP SUMMARY: ==2274== in use at exit: 41,631 bytes in 1,520 blocks ==2274== total heap usage: 34,049 allocs, 32,529 frees, 715,258 bytes allocated ==2274== ==2274== LEAK SUMMARY: ==2274== definitely lost: 0 bytes in 0 blocks ==2274== indirectly lost: 0 bytes in 0 blocks ==2274== possibly lost: 0 bytes in 0 blocks ==2274== still reachable: 41,631 bytes in 1,520 blocks ==2274== suppressed: 0 bytes in 0 blocks ==2274== Reachable blocks (those to which a pointer was found) are not shown. ==2274== To see them, rerun with: --leak-check=full --show-reachable=yes ==2274== ==2274== For counts of detected and suppressed errors, rerun with: -v ==2274== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 6 from 6) As my guess, the valgrind report no memory leak. Any way, I would like to close this topic. Thank you for your support so far. *Best Regards,* *Thuan* On Wed, Jul 16, 2014 at 8:26 PM, Chris Down <ch...@chrisdown.name> wrote: > Hi Tran, > > I think you've misunderstood the intent of Chet's reply. Nobody disagrees > that the RSS should not increase. The reason that you're being asked for > valgrind output is because the problem has yet to be reproduced, and the > valgrind output might shed some light on where the problem lies, since > others are not able to reproduce the problem. >