CODEWITHSUNDEEP
cmemory-leaksopensslvalgrindevp-cipher
Chirality
Chirality

Reputation: 745

OpenSSL EVP Leaking Bytes

I'm using OpenSSL's EVP routine and can not eliminate all still reachable memory. The tutorial linked above leaks this much:

==30413== LEAK SUMMARY:
==30413==    definitely lost: 0 bytes in 0 blocks
==30413==    indirectly lost: 0 bytes in 0 blocks
==30413==      possibly lost: 0 bytes in 0 blocks
==30413==    still reachable: 2,200 bytes in 27 blocks
==30413==         suppressed: 0 bytes in 0 blocks

and with the addition of the answer here, I was able to get it down to:

==30437== LEAK SUMMARY:
==30437==    definitely lost: 0 bytes in 0 blocks
==30437==    indirectly lost: 0 bytes in 0 blocks
==30437==      possibly lost: 0 bytes in 0 blocks
==30437==    still reachable: 744 bytes in 13 blocks
==30437==         suppressed: 0 bytes in 0 blocks

Is it possible to eliminate these? Is it something I should even bother with?

I've seen conflicting answers on SO stating that "still reachable" memory is a memory leak and others saying it isn't, hence my confusion.

Upvotes: 0

Views: 199

Answers (0)

Related Questions