On Mon, Oct 26, 2009 at 15:12, Tshepang Lekhonkhobe<tshepang gmail com> wrote:
Hi, Seems like TST isn't releasing memory. I tested using this command: Âvalgrind --leak-check=full --show-reachable=yes --leak-resolution=high -v /usr/bin/tracker-search-tool
I instead used this cmd: G_DEBUG=gc-friendly G_SLICE=always-malloc valgrind --leak-check=full --show-reachable=yes --leak-resolution=high -v --log-file=/home/wena/valgrind.log /usr/bin/tracker-search-tool 1. and then getting this before any search: ==12255== LEAK SUMMARY: ==12255== definitely lost: 2,837 bytes in 18 blocks ==12255== indirectly lost: 6,752 bytes in 340 blocks ==12255== possibly lost: 14,736 bytes in 169 blocks ==12255== still reachable: 810,358 bytes in 17,942 blocks ==12255== suppressed: 12,420 bytes in 284 blocks 2. and then this after 1 simple search: ==12276== LEAK SUMMARY: ==12276== definitely lost: 9,152 bytes in 124 blocks ==12276== indirectly lost: 876,364 bytes in 600 blocks ==12276== possibly lost: 70,236 bytes in 179 blocks ==12276== still reachable: 915,001 bytes in 20,131 blocks ==12276== suppressed: 13,152 bytes in 302 blocks 3. and then this after a whole of them searches: ==9600== LEAK SUMMARY: ==9600== definitely lost: 437,531 bytes in 8,601 blocks ==9600== indirectly lost: 72,873,740 bytes in 8,740 blocks ==9600== possibly lost: 1,712,165 bytes in 386 blocks ==9600== still reachable: 964,545 bytes in 20,619 blocks ==9600== suppressed: 13,264 bytes in 304 blocks Attached, please find the log after multiple searches (no 3). -- my place on the web: floss-and-misc.blogspot.com
Attachment:
valgrind.log.7z
Description: application/7z-compressed