Closed mpowelson closed 3 years ago
I think I found it. I'll submit a PR shortly
==36055== LEAK SUMMARY:
==36055== definitely lost: 0 bytes in 0 blocks
==36055== indirectly lost: 0 bytes in 0 blocks
==36055== possibly lost: 0 bytes in 0 blocks
==36055== still reachable: 57,832 bytes in 817 blocks
==36055== suppressed: 0 bytes in 0 blocks
This gives a good explanation of valgrind memory leak.
https://stackoverflow.com/questions/3840582/still-reachable-leak-detected-by-valgrind
I am trying to track down a memory leak that I am running into when using the Tesseract planner. While I'm not sure if this is the entirety of what I was running into running these valgrind commands on the Tesseract example yields this output which appears to indicate a leak in Trajopt. If I am reading this correctly, we are losing 12 KB per freespace motion planning call.
Abridged output with the "definetly lost" records: