So you're telling me it increasing it's memory usage and continually increasing it the longer it runs is not a memory leak? Also 2.xGB+ of RAM from 90MB is not a memory leak. I thought by my understanding of memory leaks was that when a program increases it's memory usage over time and then just keeps increasing it by just being used it is/does have a memory leak. So my understanding of memory leaks is wrong correct?
Yepp, your understanding of memory leaks is simply wrong. A memory leak is when an application/program/code acquires memory from os and does not release it when it is no longer required/in use. Either because it is forgotten when it quits or because it becomes unreachable and the app is no longer able to release it (object created but the pointer lost, or whatever the cause may be). It has nothing to do with the size of that memory area, size does not matter at all, it can be 1 byte or hundreds of megs and it can be easily detected.
As long as MyDefrag takes advantage of the memory it gets from the os and it releases it when it
quits, it is not a memory leak. The
quit is the keyword here since it is designed to
quit at the moment it has done what it should and not to run indefinitely. It
may utilize information located in that memory right till the end. As we do not know how it works internally (it is not open source) we cannot assert it has a memory leak. We can say, of course, that it has an enormous memory requirement, that could be lowered somehow, or its memory management strategy may not be the best, which is a thing Jeroen surely wants to improve, he has stated that before. It was explained dozen times why is MyDefrag so greedy on memory.
But what you did was an extremely irresponsible thing to do. You should not declare something you cannot prove.
