QUOTE(baavgai @ 8 Apr, 2008 - 08:34 AM)
The google term you're looking for is
Garbage Collection.
The short version. Once an object has no reference to it, it's memory will be released. However, the system decides when, not the programmer. There are ways to beg, but they'll only get you so far. Stop complaining, it's managaged code and we're managing it, and you aren't.
Java has the identical issue, if it makes you feel any better.
Hey, I am all for the garbage collector. A month or so ago I was reading up on XNA, which is C#-based, and it discussed how the garbage collector worked, and the various states an object can be in before its removed from memory. Pretty interesting.
I just wanted to make sure I wasn't putting myself into a position where my application was going to blow up in size indefinitely after clearing the SignalList object.
Neato!
Thanks Baavgai, I try to look up questions before I ask, but I often miss things or dont understand how they are described in other locations. Hopefully my questions will benefit others, though.
| 