How Garbage collector Will behave on value type and Reference type

Question

How Garbage collector Will behave on value type and Reference type, when it will free memory value type and reference type. i am little bit confused about this can anyone explain about this, at the same time garbage collector remove free the Memory of value type or Reference type Which remove first

Answer 1

You're thinking about the problem the wrong way. Stop thinking about "value types" and "reference types". Instead, start thinking about variables, and whether those variables are short lived or long lived.

The purpose of the garbage collected heap is to reclaim the storage associated with long-lived variables. The purpose of the stack is to reclaim the storage associated with short-lived variables.

People will try to tell you that "value types go on the stack" and "references go on the heap" and so on, and this is confusing nonsense. Variables go on the stack or the heap (or registers -- everyone forgets about registers) and variables can be of value type or reference type.

You keep asking "which will the garbage collector remove first?" That question cannot be answered. The garbage collected heap makes no guarantees whatsoever about the order in which memory is reclaimed. The short-lived storage -- the stack -- will be reclaimed as activation frames are popped off the stack. However, the C# language permits the garbage collector to clean up storage that is referenced by short-lived storage before the frame is popped off the stack if the runtime can determine that the reference will not be accessed again. Basically, when storage is reclaimed is an implementation detail of the runtime, subject to change at any moment.