whtnyte-raernst wrote...
In the first place, the ummm "person" ranting about the memory leak has no concept of what he is spouting. A memory leak is when one program corrupts the memory space of another. In essence, it has "leaked" out of it's memory sandbox into the sandbox of another program running in memory.
That usually gets it labeled a virus...I don't think I would call Dragon Age a virus.
Don't know if I'm the "person" you're referring to, but since I did mention a memory leak and I did mention that I work with software, it's possible. Not sure if I can be characterized as ranting though and I know I have at least a concept about what I spout off about.

The definition you're using for memory leak isn't the common one I was aiming for with the term. With your advanced degree you probably know something I don't but your definition above isn't the one I was using.
The pretty common understanding for memory leak among those of us without advanced computer science degrees (but who none the less earn our living coding, debugging and supporting software) is when your code allocates memory but doesn't deallocate it when it's done with it so the memory becomes unavailable to any other process. These types of leaks are very common and are not referred to as virii.
Now of course not everything that acts like a memory leak IS a leak but just about everyone I know still refers to it as such if some of the basic symptoms are there.
From what I've read and experienced the symptoms here seem to match what I normally call a memory leak. Now, no one at Bioware has said such a thing exists, so I'll stop calling whatever is happening that here on the boards.
What shall we call it though?
Oh, and your later theory about holding textures just in case seems pretty plausible. Still seems like something that a dev could verify and say something about to stop us all from running around in circles.
Modifié par Sammage2k, 21 décembre 2009 - 11:38 .