Interested to Buy Any Domain ? << Click Here >> for more details...
Why doesn't the .NET runtime offer deterministic destruction
- 1 Answers
- 2135 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 |
What is the difference between using system.net and system.net.sockets?
Is it possible to combine asp.net webforms and asp.mvc and develop a single web application?
What type of filter does outputcacheattribute class represents?
What you mean by routing in asp.net mvc?
Explain the advantages and disadvantages of ASP.Net MVC over ASP.NET?
Does the .NET Framework have in-built support for serialization?
What is the 'page life cycle' of an ASP.NET MVC?
what is ssdl?
what are the aggregate functions in ASP.NET?
Why is XmlSerializer so slow
how to create session in .net
Can you explain renderbody and renderpage in asp.net mvc?
Dot Net Framework 
