Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
If an object is not referenced by any other, then it is subject to be collected by the .NET CLR garbage collector.
However, if objA references objB, objB references objC, and objC references back to objA, how does the garbage collector figure out that they (as a whole) can be collected?
The CLR uses a technique known as mark-and-sweep.
As part of this technique, every object can be thought of as initially marked for collection. Then, the CLR goes through each accessible object, starting with your globals (static fields, etc.) as the roots, and clears the mark on each walkable object. It then sweeps the remaining marked objects.
Keep in mind that this “marking” is conceptual; in reality, the objects are most likely added to a collection-set.
In the case of looping self-referenced objects, no reference to the objects will be found from the application, and so the algorithm will never reach those objects to “unmark” them.