How to check if garbage collection works well?

Question

go

Now the application starts with a memory consumption of 1.5 Mb, when checking (manually connecting from the client, trying to generate the maximum load) it gradually grows to 8-9 Mb and stops at this mark (even if I continue to create chaos with the client).
There is one more thing, in theory, the application should free up memory (by unloading unused parts), but over time, consumption does not decrease (judging by the task manager).
So the question is: how to make sure that the memory does not run away, and if everything is fine, then why does the consumption stop at 8 MB instead of decreasing to the initial level?

Answer 1

It should not release unless the system asks. This is how most assemblers work, they give memory "back to the program".

Answer 2

freeing memory is an extremely resource-intensive process. therefore, it is produced by the garbage collector only at the urgent request of the system itself, well, or regularly, when there is no other load at all

Answer 3

What OS and what language are you using?

Answer 4

The garbage collector may not physically release the memory if it once needed 8 MB to work. There is a chance that this volume will be needed again, in which case the program will run faster if the objects have already been created. There is also such a thing as memory fragmentation. Part of the memory may not be used at all and be reserved for compacting objects, for example, it depends on the type of GC. Some details here for example.