The environment - I guess you mean the status bar at the bottom - is sometimes slow to show released memory. I don't know if calling Kernel.Collect is delayed, or if reporting the result is delayed. But it can take a few unrelated trivial actions (like moving a Window) before this happens; unloading the module is not necessary.dmaksimiuk wrote:2. When the garbage collector should claim all the memory back? ...
... the environment still showed allocated memory around 670_000_000 bytes.
I don't think there is a problem here as the memory is released when necessary. See, for example, the DoMany command in my previous post where all the memory is automatically released 100 times within the FOR loop.