Why doesn't the .NET runtime offer deterministic destruction
- 1 Answers
- 1606 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 |
Explain what is the difference between view and partial view?
How can I tell what .net framework is installed?
What is the difference between tempdata and viewbag?
What is strong name and which tool is used for this ?
4 Answers Accenture, BirlaSoft,
Can you set the unlimited length for "maxjsonlength" property in config?
Explain .Net Framework? Why we use it?
What is entitytype? : Entity framework
mention in what all scenarios entity framework can be applicable?
How we can call a JavaScript function on the change of a Dropdown List in ASP.Net MVC?
What is the difference between partial and renderpartial?
What is net framework 3.0 ?
sql related question (outer join, left, right etc) array vs hashtable CRL sqldatareader vs dataset what is WPF, WCF, compare to WinForms Webservices Asp.net MVC vs WebForms?
Dot Net Framework 
