01-23-2012, 08:14 AM
RDCA Wrote:the only way to cause an issue is by just referencing random stuff that will not be disposed until close to the end of the app
This is the way that variables being created in heap memory work though. It's what I was trying to explain in the first post I made about that memory leak. To avoid having a bunch of variables that DON'T get destroyed from memory until the end of the program, an application should always take care of variables that are no longer in use, even if it means you re-create them later on for the few seconds that you're going to use it. That's code optimization right there. If not, and you end up re-creating a new instance of the same type several times through your program for no reason, that's what a memory leak is.