Skip to content
New issue

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

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

Already on GitHub? # to your account

Memory leaks #3

Open
JBouron opened this issue Nov 2, 2017 · 0 comments
Open

Memory leaks #3

JBouron opened this issue Nov 2, 2017 · 0 comments

Comments

@JBouron
Copy link

JBouron commented Nov 2, 2017

Sample output :

==19564== Memcheck, a memory error detector
==19564== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==19564== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==19564== Command: ./pixelsort -i test.png -o test.png -t127
==19564== 
Processing…
Writing…
==19564== 
==19564== HEAP SUMMARY:
==19564==     in use at exit: 345,566 bytes in 19 blocks
==19564==   total heap usage: 718 allocs, 699 frees, 2,146,850 bytes allocated
==19564== 
==19564== LEAK SUMMARY:
==19564==    definitely lost: 3,392 bytes in 4 blocks
==19564==    indirectly lost: 342,174 bytes in 15 blocks
==19564==      possibly lost: 0 bytes in 0 blocks
==19564==    still reachable: 0 bytes in 0 blocks
==19564==         suppressed: 0 bytes in 0 blocks
==19564== Rerun with --leak-check=full to see details of leaked memory
==19564== 
==19564== For counts of detected and suppressed errors, rerun with: -v
==19564== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)```
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant