Re:Comparing C and C++ usage and performance with a real wor...
by CJefferson on Sunday September 03, 2017 @02:33PM
(#15163017)
The problem with counting leaks is it counts memory you need until the very end of your program. There is no point calling free as you are exiting anyway, and I have seen programs where freeing everything took .5 seconds as the program was closing.
[ Parent
| on HN ]
Re:Comparing C and C++ usage and performance with a real wor...
by nitrogen on Sunday September 03, 2017 @03:09PM
(#15163225)
As someone whose startup was probably hindered by an almost religious adherence to testing with Valgrind (hardware was way too slow), I'd still say finding the real leaks and bugs is a lot easier when you don't have the noise of "expected" leaks.