I just believe we work in very different environments. We had problems with compilers having memory leak. The software I write, runs for weeks or even months w

I just believe we work in very different environments. We had problems with compilers having memory leak. The software I write, runs for weeks or even months without being restarted. Yeah, the original problem of memory leak, or even resources leaks in general is still very very real in some field. Now, of course if you use python or golang, or javascript, basically you will never have a real memory leak. But this is not a good reason for calling bad use of resources "a memory leak". BTW: > First and foremost, the problem the original definition points out doesn't exist any more. When a program dies, all the resources it allocated, file descriptors, memory, ports etc will safely be cleaned by the OS. Any modern OS that doesn't do so will consider this a bug. So there is no practical reason to sweat the original problem. Memory leak never concerns the OS, like never. When the OS allocate memory to a software then is the software responsibility to deallocate it, returning it to the OS. > Any modern OS that doesn't do so will consider this a bug. This is true but it is not what we are discussing. Anyhow, I am just trying to help you understand what people usually means with "memory leak" because you seems a little confused. But if you are sure and you are definitely not confused and you think that it is me being wrong, I am not going to engage in any discussion. Cheers,