Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tests leaking memory #6

Closed
stephenmathieson opened this issue Aug 24, 2015 · 3 comments
Closed

tests leaking memory #6

stephenmathieson opened this issue Aug 24, 2015 · 3 comments
Labels

Comments

@stephenmathieson
Copy link
Contributor

looks like there are a few memory leaks/invalid reads that should be addressed:

$ valgrind ./test --leak-check=full
[ ... ]
==5700== 
==5700== HEAP SUMMARY:
==5700==     in use at exit: 566 bytes in 55 blocks
==5700==   total heap usage: 116 allocs, 61 frees, 1,067 bytes allocated
==5700== 
[ ... ]
==5700== LEAK SUMMARY:
==5700==    definitely lost: 566 bytes in 55 blocks
==5700==    indirectly lost: 0 bytes in 0 blocks
==5700==      possibly lost: 0 bytes in 0 blocks
==5700==    still reachable: 0 bytes in 0 blocks
==5700==         suppressed: 0 bytes in 0 blocks
==5700== 
==5700== For counts of detected and suppressed errors, rerun with: -v
==5700== ERROR SUMMARY: 95 errors from 22 contexts (suppressed: 2 from 2)

here's the full valgrind report that shows what's happening in more detail.

@h2non h2non added the bug label Aug 24, 2015
@h2non
Copy link
Owner

h2non commented Aug 24, 2015

Ouch! Thanks a lot, will take a look asap!

h2non added a commit that referenced this issue Aug 24, 2015
@h2non
Copy link
Owner

h2non commented Aug 24, 2015

This should be fixed now. See: 8c011f2

@h2non h2non closed this as completed Aug 24, 2015
@stephenmathieson
Copy link
Contributor Author

awesome!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants