Revision history [back]

After running the binary in segmentationClustering_noGPU_leak, valgrind reports no leak

==3848== HEAP SUMMARY:
==3848==     in use at exit: 47,332 bytes in 242 blocks
==3848==   total heap usage: 20,497,664 allocs, 20,497,422 frees, 273,052,625,181 bytes allocated
==3848== 
==3848== LEAK SUMMARY:
==3848==    definitely lost: 0 bytes in 0 blocks
==3848==    indirectly lost: 0 bytes in 0 blocks
==3848==      possibly lost: 4,676 bytes in 83 blocks
==3848==    still reachable: 42,656 bytes in 159 blocks
==3848==         suppressed: 0 bytes in 0 blocks
==3848== Rerun with --leak-check=full to see details of leaked memory

I'm using opencv-2.4.8 and valgrind 3.8.1 on Ubuntu 13.10 64bit.