Memory leaks - valgrind about seamly2d HOT 5 CLOSED

Original comment by Roman Telezhynskyi (Bitbucket: dismine, GitHub: dismine):

Yes, you can try to fix memory leaks. We will help you if you'll show us code that leaks.

from seamly2d.

Original comment by Abhishek Kumar (Bitbucket: _slytherin, GitHub: Unknown):

I used valgrind on my updated code .Its showing memory leaks.If I can help in fixing them any way please guide me.

HEAP SUMMARY:
==5040== in use at exit: 1,820,478 bytes in 21,635 blocks
==5040== total heap usage: 219,347 allocs, 197,712 frees, 56,571,499 bytes allocated
==5040==
==5040== LEAK SUMMARY:
==5040== definitely lost: 3,240 bytes in 18 blocks
==5040== indirectly lost: 27,002 bytes in 762 blocks
==5040== possibly lost: 40,061 bytes in 585 blocks
==5040== still reachable: 1,574,703 bytes in 19,391 blocks
==5040== suppressed: 0 bytes in 0 blocks

from seamly2d.

Original comment by Roman Telezhynskyi (Bitbucket: dismine, GitHub: dismine):

Last test doesn't show any memory leaks. :)

from seamly2d.

@DSCaskey - should we close this?

from seamly2d.

from seamly2d.