[Closed] DotNet Memory Leak

I don’t know why the maxGeneration trick is needed. From what I understood from the dotNet help calling Collect() and Collect with maxGeneration should yield the same result, but in my tests I got different results when using the 2 ways, so I stuck to the one that worked best.

Well the help states that GC is performed on the most recent objects to be collected and calling the MaxGeneration parameter will ensure that all generations will be collected. I find it a bit odd that the newest will be more likely to be collected then the old. Not sure of the logic of that one. When I get a chance I will see if I can find out any more with your test.