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.

>>25
Look, it's easy to see that you are right. But the fact is it basically took you two days to find the issue. The problem is in C language. Not the programmer.