4 ms·
That's still a memory leak. It's just caused by a logic error that a compiler couldn't ever catch.
by viscanti 10y ago
That's still a memory leak. It's just caused by a logic error that a compiler couldn't ever catch.
- wyldfire 10y agoWell, you might think it's a distinction without a difference but in fact it's not a leak. A leak only occurs when the handle one might use to deallocate memory/resources is itself deallocated. Whether "I added one FramistanObject to the FramistanObjectLog for every single HTTPConnection" is a logic error or not depends on what the intended design was.
- okasaki 10y agoValgrind calls that an indirect leak (stuff that wasn't freed at exit but is referenced by stuff that also wasn't freed)