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.

>>8
1. I do, always use custom allocators and efficient memory pools
2. No, it is extremely dependent on OS
3. Can't time real time applications like high performance databases or games
4. It is always waste of time to write a module from scratch if there is already popular one with BSD-like license. If you are on embedded platform, maybe you have to write a custom one.
5. xd