Why doesn't the .NET runtime offer deterministic destruction
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 |
What are Action Methods in ASP.NET MVC?
What are the main features of asp.net mvc 4 used by asp.net web api?
what is csdl?
What are the levels at which filters can be applied in an asp.net mvc application?
What is meant by viewdata?
Explain how you can implement Ajax in MVC?
How large is the .net framework 3.0?
Do you know about the new features in asp.net mvc 4 (asp.net mvc4)?
What is the difference between STA and MTA?
What is the use of view model in asp.net mvc?
what is the three pillar of .Net ?
What are the types of assemblies and where can u store them and how ?
11 Answers Accenture, BirlaSoft, IBM,