Valgrind log for 2008-12-28

Case number:671071-778850
Topic:Game: Other
Opened by:gringer
Status:Closed
Type:Bug
Opened on:Sunday, December 28, 2008 - 06:14
Last modified:Wednesday, April 8, 2009 - 16:42

Hello,

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==
==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)

(Sun, 12/28/2008 - 06:14  |  4 comments)


xiando's picture
User offline. Last seen 7 years 21 weeks ago. Offline
Joined: 10/19/2008
Groups: Oma Gawd

a comparably thorough testing utility for Wintel machines? If so, It would be nice if you could provide a link, so that similar information can be posted on the windows client.

That is, I believe you're running Linux, yes?

thanks,

xiando

gringer's picture
User offline. Last seen 2 years 14 weeks ago. Offline
Joined: 10/15/2008
Groups: xkcd

There is no Windows port of Valgrind (http://en.wikipedia.org/wiki/Valgrind#Platforms_supported). Something like BoundsChecker or Purify (http://www-01.ibm.com/software/awdtools/purify/win/) may work, and there is apparently an attempt in getting Valgrind working with Wine (which would pick up memory errors in Windows clients running on Linux via Wine). It's likely that you'd need to pay a bit of money to obtain a similar memory checking tool for Windows, but I haven't researched that at all.

Regardless of this, if the code is reasonably cross-platform, many of the errors identified on one platform should be transferable to others. Obviously in this case, you're not going to get the alsa or video card driver errors happening in Windows, but other errors that seem to be in foldit code may be an issue on all three platforms.

xiando's picture
User offline. Last seen 7 years 21 weeks ago. Offline
Joined: 10/19/2008
Groups: Oma Gawd

Thank you for the reply. Based on what you're saying about the error sources, any check on Windows will likely result in a duplication of effort, so I'll just leave be with your post.

admin's picture
User offline. Last seen 46 weeks 6 days ago. Offline
Joined: 11/10/2007
Groups: vi users
Status: Open » Closed

Thank you for the log. With the current version, it has outlived its usefulness, so I am closing this issue.

Sitemap

Developed by: UW Center for Game Science, UW Institute for Protein Design, Northeastern University, Vanderbilt University Meiler Lab, UC Davis
Supported by: DARPA, NSF, NIH, HHMI, Amazon, Microsoft, Adobe, Boehringer Ingelheim, RosettaCommons