rspec/rules/S1215/csharp/rule.adoc

36 lines
1022 B
Plaintext

== Why is this an issue?
Calling ``++GC.Collect++`` is rarely necessary, and can significantly affect application performance. That's because it triggers a blocking operation that examines _every object in memory_ for cleanup. Further, you don't have control over when this blocking cleanup will actually run.
As a general rule, the consequences of calling this method far outweigh the benefits unless perhaps you've just triggered some event that is unique in the run of your program that caused a lot of long-lived objects to die.
This rule raises an issue when ``++GC.Collect++`` is invoked.
=== Noncompliant code example
[source,csharp]
----
static void Main(string[] args)
{
// ...
GC.Collect(2, GCCollectionMode.Optimized); // Noncompliant
}
----
ifdef::env-github,rspecator-view[]
'''
== Implementation Specification
(visible only on this page)
include::../message.adoc[]
'''
== Comments And Links
(visible only on this page)
include::../comments-and-links.adoc[]
endif::env-github,rspecator-view[]