Not a memory leak exactly. A memory leak is when memory keeps getting used but never gets reclaimed. In this situation, memory will keep getting used, but it will just take a while for the garbage collector to get around to reclaiming it. The effect on system memory usage is essentially the same though: it fills it up. In this case, the garbage collector will eventually get around to reclaiming that memory meaning you won't run out of memory because of this, but you very well may see a substantial performance hit since the garbage collector will be working overtime.
I replied earlier to your refernced thread in reguards to using a delegate to prevent this behavior.
|