Valgrind log for 2008-12-28
|Opened on:||Sunday, December 28, 2008 - 06:14|
|Last modified:||Wednesday, April 8, 2009 - 16:42|
I'm attaching a valgrind log (memory access check) for foldit, carried out on Sun, 28 Dec 2008 ~19:05 +1300. I ran the program via 'valgrind ./Foldit' and clicked quit as early as possible (i.e. at the connect online/offline screen) to generate this log.
Here are the summaries from the bottom of the log:
==3601== ERROR SUMMARY: 214809 errors from 711 contexts (suppressed: 1516 from 7)
==3601== malloc/free: in use at exit: 18,213,154 bytes in 32,436 blocks.
==3601== malloc/free: 250,201 allocs, 217,767 frees, 91,547,944 bytes allocated.
==3601== For counts of detected errors, rerun with: -v
==3601== searching for pointers to 32,436 not-freed blocks.
==3601== checked 21,788,808 bytes.
==3601== LEAK SUMMARY:
==3601== definitely lost: 23,021 bytes in 168 blocks.
==3601== possibly lost: 45,461 bytes in 1,260 blocks.
==3601== still reachable: 18,144,672 bytes in 31,008 blocks.
==3601== suppressed: 0 bytes in 0 blocks.
A lot of these errors/leaks seem to be in libasound.so and i915_dri.so (my video card is Intel Corporation Mobile 945GM/GMS, 943/940GML), but there's still plenty that appear to originate within the foldit code itself.
Hope this helps,
David Hall (gringer)