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.

>>18
The problem is that you are an idiot who can't follow simple rules.

Does fibs use allocating functions? —(yes, malloc)→ Does it always free the memory? —(no)→ fibs is an allocating function.
Is all memory allocated within fibs reachable in the end —(no, inner fibs calls allocate but aren't freed)→ fibs leaks.

Don't use C if you are too stupid for basic things like these.