Why doesn't the .NET runtime offer deterministic destruction
- 1 Answers
- 1196 Views
- I also Faced
- E-Mail Answers
Answer / kirti
Because of the garbage collection algorithm. The .NET garbage collector works by periodically running through a list of all the objects that are currently being referenced by an application. All the objects that it doesn't find during this search are ready to be destroyed and the memory reclaimed. The implication of this algorithm is that the runtime doesn't get notified immediately when the final reference on an object goes away - it only finds out during the next sweep of the heap.
Futhermore, this type of algorithm works best by performing the garbage collection sweep as rarely as possible. Normally heap exhaustion is the trigger for a collection sweep.
| Is This Answer Correct ? | 0 Yes | 0 No |
Difference between int and int32
Can I add mvc testcases in visual studio express?
About DTS package ?
1 Answers Accenture, Grafotech,
Do you know about the new features in ASP.Net MVC 4 ?
What is page life cycle?
mention in what all scenarios entity framework can be applicable?
How do you handle variable number of segments in a route definition?
What are child actions in ASP.Net MVC?
Which is the institute which also caters to your personal development other than subject.
what is a mvc in asp.net?
3 Answers Cap Gemini, Elsinoir Technologies, HCL,
How does the .net framework 3.0 relate to the .net framework 2.0?
What are scaffold templates in mvc?
Dot Net Framework 
