On Monday, 15 December 2014 at 14:39:50 UTC, Daniel Murphy wrote:
"Stephan Schiffels" wrote in message
news:[email protected]...
This doesn't work for me, for some reason. I reserve via
GC.reserve(4_000_000_000), ensured that it does return at
least that amount, but the Garbage collector will still
collect like crazy, long before that reserved memory is
exhausted...
That's strange, I must be missing something. Hopefully one of
the GC experts can explain why this happens.
Perhaps the reserve pool is empty when the next collection runs
and ends up being returned to the OS?
