Time to use GC.Collect with caution

While it is not usually recommended to call GC.Collect() directly, in some specific cases, this is reasonable. For example, when a service runs in a circular manner and is idle for a long time after executing a task, it is possible to optimize resource utilization when it is forced to garbage collection during the idle phase to free up memory occupied by the process that is about to fail.

Another acceptable situation is after closing a large form in a GUI application. Since all UI controls meet garbage collection at this time, and the short performance drop during form closing users may not notice it, it is reasonable to start GC collection.

In addition, the following situations may also require consideration of calling GC.Collect():

• When you have solid evidence that a large number of objects (especially Gen 1 and Gen 2 objects) are ready for garbage collection, and that the performance impact is minimal.
• Starting from .NET 4.5, when entering or exiting GCLatencyMode.LowLatency or GCLatencyMode.SustainedLowLatency is recommended to enforce full GC using GC.Collect(2, GCCollectionMode.Forced) when entering or exiting
GCLatencyMode.SustainedLowLatency
• . Using .NET 4.6, you can use the
GC.TryStartNoGCRegion

These exceptions emphasize the importance of caution when calling

. It is important to evaluate the specific environment and potential performance impact before making this decision.