zgrssd -> RE: Working as intended? (6/15/2020 3:37:56 PM)
|
quote:
ORIGINAL: Vic I dont think so. Is it permanent? or does it go down after time? We are dealing with .NET, so Garbage Collection Memory Management. Memory Measurements are notoriously hard to do right. And issues even worse to diagnose. So the usual Spiel so people do not missunderstand the GC: Garbage Collection is expensive. While it runs, all other threads must pause. As a result .NET is really lazy at running the GC. If it only happens once - on application closure - that is the ideal case. Beyond that, only a few cases can get it to run: - danger of a OutOfMemoryException. When you get one, the GC did all the collection and defragmentation it could. - explicit calls of GC.Collect(). But really does not belong into production code. - various optimisations. Concurrent/Server Garbage Collection. Automatic passes over generation 1 after leaving certain scopes. Taskmanager memory usage: 200 MiB during intro sequence 183 MiB in main menu just shy of 800 MiB after loading a large moon
|
|
|
|