How the fuck do people even get memory leaks?

Especially when tools like valgrind, dr. memory, gperftools exist. When I write C code, I write tests for most non-trivial shit. After I compile, I run valgrind. Boom. Immediately I know to fix a mem leak before it gets out of hand and too hard to trace.

Can it be true? Are mem leaks purely due to programmer laziness? Too fucking lazy to run a small piece of software LMAO. Go fuck yourselves.

>>7
1.you obviously don't write programs larger than a few pages
2.modern malloc is fast and reliable
3.the allocations can be timed to reduce performance impact.
4.if you really need a custom allocator don't invent wheels: there are special purpose allocators and structures debugged, benchmarked and unit-tested already.
5.you are going to ignore the above and write crappy allocator when you finally need one, because everything else is too mainstream.